Maltweb multi-axis viewing interface and higher level scoping

ABSTRACT

A method, apparatus and computer program product for navigating in a multi-dimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language are disclosed. A selected predefined portion is displayed in a first display region. A point on a primary axis of the multi-dimensional space corresponding to the displayed pre-defined portion is also displayed. Also, a method, apparatus and computer program product for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language are also disclosed. Predefined portions are stored in terminal nodes. Higher level nodes are provided for organising the terminal nodes into an hierarchical structure embodied in said electronic publication. Each higher level node contains the identity of a parent node, a position indicator for the higher level node and an associated identifier.

REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 09/689,927, filed on Oct. 12, 2000, now allowed, which is a continuation-in-part of U.S. application Ser. No. 09/108,999, filed on Jul. 1, 1998, now U.S. Pat. No. 6,233,592, which is a continuation of International Application No. PCT/AU1998/000050, filed Jan. 30, 1998, which designated the United States and was published in English, and which claimed priority to Australian Application No. PO4892, filed on Jan. 31, 1997. Each of these applications, in their entirety, are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to an electronic publishing system, and in particular to an electronic publishing system for the delivery of information which is not limited as to storage space and is not governed by predetermined pathways.

The present invention relates generally to an electronic publishing system and, in particular, to aids for navigating in an electronic publishing system and a method of organising data in an electronic publishing system.

BACKGROUND

Conventionally, information is published in document form as a printed publication, or in electronic form but again using the document or book metaphor. In the past, the concept of a “multidimensional space” in electronic publishing has been intuitively understood (that is, instinctively desired). However, a comprehensive display, discussion or treatment has been rejected by publishers and information providers as too difficult to develop and manage. Instead, publishers and information providers have managed large amounts of data:

(1) by limiting the size or coverage of the information space; and

(2) by setting or predetermining the path through that information space.

The effect of this is clearest when the dimension of time is considered. The conventional approach to information storage and publishing is centred on the notion that information is either “current information” (ie, present day) or “historical information” (ie, the day before the present day and all days prior to that). Thus, information is traditionally retained (stored) and/or published (sold) as either current or historical information.

The effect of this has been to leave the end user with a collection of non-integrated repositories and many additional tasks to do before the information is useful to them. For example, the end user is required to:

(1) make most of their own connections between related pieces of information;

(2) do their own analysis of the type and subject of information they require or are seeking; and

(3) find information appropriate to the point in, or period of, time with which they are concerned.

To illustrate the disadvantages of conventional publishing systems, an example of using such conventional techniques and publishing systems to research information is provided. If a person were interested in information regarding the powers of the Secretary under Australian legislation with respect to couples in a family relationship, when and how the Secretary is restricted, and what did the relevant legislation provide prior to that, the person would refer to relevant legal information, which is the Social Security legislation of the Commonwealth of Australia. The relevant provisions are set forth in Appendix A under the heading “Example Research”. This would be determined by the end user's own knowledge of the broad subject and/or reference to secondary material.

The relevant legislative provision is Section 4, which in conventional electronic legal publishing systems might be found by looking for words or phrases such as “family”, “family relationships”, and “family relationships” AND “social security”, where AND is a logical operator.

Once the above is established, it can be seen from the information found that Section 4 of the Social Security Act, as at Sep. 8, 1996, has been amended ten times (see Appendix A: A1. AMENDMENTS TO SECTION AT Sep. 8, 1996).

There is however nothing in the current Commonwealth Government Reprint, in either the electronic or print versions (see heading EXAMPLE RESEARCH of Appendix A), that allows the end user to see the text of those amendments or what part(s) of Section 4 were changed by them.

Thus, unless the end user is prepared to refer to many statute books, reading each piece of text against another, the end user is not able to see easily or reliably what section 4 looked like before it was amended by any one of a number of prior amending Acts. However, if the end user has a library complete enough to provide access to the prior amending Acts, the person would eventually determine that Act No 105 of 1995 is the relevant amending Act.

Further, it should be noted that, while the Commonwealth Government Reprint indicates that the Social Security Act was amended by Act No 105 of 1995, it does not indicate what section or schedule in Act No 105 of 1995 actually amended Section 4. This again requires the end user to have access to the amending Acts themselves and renders the information provided by the Reprint as to commencement (see Appendix A: B. COMMENCEMENT INFORMATION FOR ACT NO 105 OF 1995 CONTAINED IN REPRINT) of little utility without a copy of the amending Act No 105 of 1995 from which it can be established that Section 14 of Act No 105 amended Section 4 of the Social Security Act with respect to powers of the Commissioner (see Appendix A: D. AMENDING ACT 1995 NO 105 AMENDING SECTION 14).

Eventually, the required information can be found but several pieces of information need to be searched by the end user. This is an arduous, time consuming, tedious and complex task that must be manually repeated for each research topic and if the same search is to be carried out again.

Conventional publishing systems, including electronic publishing systems that typically are speeded-up, paper-based publishing systems, are based on a book-metaphor. The smallest piece of information used by such conventional publishing systems is either (I) an Act or Regulation (in the case of reprints, a whole Act or Regulation is printed again), or (II) a word. Typically, conventional publishing systems choose a word as the smallest piece when legislation is amended. To track such amendments, a lawyer or their assistant may actually use scissors to cut and paste pieces of legislation or the publisher cuts and pastes each word electronically. If a whole Act or Regulation is tracked as in (I) above, it is necessary to store each new version of an Act or Regulation in its entirety.

This has a number of consequences, including:

a) only a few versions of each Act or Regulation are stored;

b) the end user rarely searches more than one reprint at a time;

c) it is very difficult to know which particular section or schedule has changed, to track how that particular section or schedule has changed, to find the relevant section of the Amending Act or Regulation that effected the section or schedule as shown in the reprint;

d) if multiple changes have occurred on a particular section or schedule between reprints, the latest version of the section or schedule can only be seen in the reprint;

e) issues like commencement of the latest version of a particular section or schedule and so-called “Application, Saving or Transitional Provisions” are difficult to recreate; and

f) it is difficult to come to a full understanding of the legislation by means of the reprints.

If every single word is tracked, as in (II) above, a level of complexity results that is difficult to administer and maintain without a large number of errors. For example, some legislative sections and schedules are amended several times annually.

Table 1 provides an example where Section 6 of the Income Tax Assessment Act has been amended 70 times:

TABLE 1 S. 6 am. No. 88, 1936; No. 30, 1939; No. 50, 1942; No. 3, 1944; No. 6, 1946; No. 44, 1948; No. 48, 1950; No. 1, 1953; No. 65, 1957; No. 55, 1958; No. 85, 1959; Nos. 18 and 108, 1960; No. 17, 1961; No. 69, 1963; No. 110, 1964; No. 103, 1965; No. 85, 1967; Nos. 4, 60 and 87, 1968; No. 93, 1969; No. 54, 1971; Nos. 51 and 164, 1973; No. 216, 1973 (as am. by No. 20, 1974); No. 126, 1974; Nos. 80 and 117, 1975; Nos. 50, 143 and 205, 1976; Nos. 87 and 172, 1978; No. 27, 1979; No. 24, 1980; Nos. 108 and 154, 1981; No. 103, 1983; Nos. 47 and 123, 1984; No. 168, 1985; Nos. 41, 48, 52 and 154, 1986; No. 138, 1987; Nos. 73, 97, 105 and 107, 1989; Nos. 20, 35 and 135, 1990; Nos. 4, 5, 100 and 216, 1991; Nos. 80, 98 and 224, 1992; Nos. 17, 18, 57 and 82, 1993; Nos. 138 and 181, 1994; Nos. 5 and 169, 1995

It is both difficult and impractical to store the complete amendment history of every word and phrase within section 6. Trying to track all changes on such a detailed level leads to unmanageable complexity.

Largely, the split between historical and present information has come about because of the publishing and information industry's own development, and not because such is the desired or best way to manage information. Thus, a need clearly exists for an electronic publishing system that can overcome one or more of the disadvantages of conventional techniques and systems.

International Publication No. WO 98/34179 (PCT/AU98/00050), corresponding to U.S. patent application Ser. No. 09/108,999, is incorporated herein by cross reference and discloses an electronic publishing system that provides a sparse multidimensional matrix of data using a set of flat file records. In particular, the computer-implemented system publishes an electronic publication using text-based data. Predefined portions of the text-based data are stored and used for the publication. At least one of the predefined portions is modified, and the modified version is stored as well. The predefined portion is typically a block of text, greater in size than a single word, but less than an entire document. Thus, for example, in the case of legislation, the predefined portion may be a section of the Act. Each predefined portion and the modified portion(s) are marked up with one or more links using a markup language, preferably SGML or XML. The system also has attributes, each being a point on an axis of a multidimensional space for organising the predefined portions and the modified portion(s) of the text-based data. This system is simply referred to as the Multi Access Layer Technology or “MALT” system hereinafter.

Existing methods of navigating electronic publications have been derived from traditional methods used to navigate printed publications. Typical of these methods is the use of a bookmark, which is merely an indicator which identifies a page or section of interest. Bookmarks are typically limited in the information provided to users. Bookmarks follow a single axis, perhaps indicating the current page, chapter and title of the publication. However, bookmarks do not necessarily provide the user with adequate context pertaining to how the user arrived at the current page. If a user knows the exact publication desired and then navigates through the same publication, a bookmark is probably adequate for the user's needs. In the event that the user has conducted a number of searches and trawled through various versions of different documents to arrive at the current page of a publication, it is impossible for a bookmark to capture all the relevant information and provide the user with an adequate reading context. The book metaphor fails to address the abilities and complexities of electronic publications.

Existing methods of navigating compact disc based publications and Internet sites are typically ill-suited to displaying the complex data provided by MALT. Known web solutions, for example, typically handle two axes, sequential and hierarchical, using either embedded links such as Previous, Next and Contents, or expandable content frames, as provided in Windows Explorer. Further axes may be handled by incorporating embedded links in the body of the text. Such embedded links are point to point, and provide limited navigational value to the user.

Object databases are capable of providing the required functionality, but search queries employed by these databases are too complicated for untrained users, both in terms of the complexity and amount of information required.

Thus, a need clearly exists for a detailed context to be provided to users of electronic publishing, overcoming one or more disadvantages of existing systems.

SUMMARY

In accordance with a first aspect of the invention, there is provided a system for publishing electronic information, comprising:

a plurality of predefined portions of data with each predefined portion being encoded with at least one linking means, and, for each predefined portion, the each predefined portion is stored and, where such predefined portion has been modified, each such modified predefined portion is stored; and

a plurality of attributes, each attribute being a point on an axis of a multidimensional space for organising the data.

In accordance with a second aspect of the invention, there is provided a recording medium for publishing electronic information, comprising:

a plurality of predefined portions of data with each predefined portion being encoded with at least one linking means, and, for each predefirmed portion, the each predefined portion is stored and, where such predefined portion has been modified, each such modified predefined portion is stored; and

a plurality of attributes, each attribute being a point on an axis of a multidimensional space for organising the data.

In accordance with a third aspect of the invention, there is provided a method for publishing electronic information, comprising:

providing a plurality of predefined portions of data with each predefined portion being encoded with at least one linking means, and, for each predefined portion, the each predefined portion is stored and, where such predefined portion has been modified, each such modified predefined portion is stored; and

providing a plurality of attributes, each attribute being a point on an axis of a multidimensional space for organising the data.

According to a first aspect of the invention, there is provided a method of navigating in a multidimensional space having three or more dimensions. The method includes the steps of:

displaying in a first display region a selected predefined portion of an electronic publication formed from predefined portions of text-based data encoded using a markup language, each predefined portion having at least one attribute being a coordinate of an axis of the multidimensional space, wherein logical connections among the predefined portions, and any logical connections between the predefined portions and predefined portions of any further electronic publication data in the multidimensional space, correspond to one or more axes of the multidimensional space;

displaying a point on a primary axis of the multidimensional space dependent upon an attribute of the displayed predefined portion;

displaying a second point on a second, viewing axis orthogonal to the first axis, the second point being derived from the first point dependent upon a logical connection between the displayed predefined portion and a predefined portion associated with the second point; and

displaying information regarding the second point of the second axis in a second display region, the first and second points being displayed in two display regions.

According to a second aspect of the invention, there is provided a method of navigating in a multidimensional space having three or more dimensions, the multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The method includes the steps of:

providing a view comprising at least two anchor sets;

displaying at least one base point and at least a first axis depending from the base point;

displaying at least one of a further point and an axis derived from the base point;

navigating a multidimensional space formed by the points and axes;

returning to the base point when required; and

adjusting the view so a current view point becomes a new base point.

According to a third aspect of the invention, there is provided an apparatus for navigating in a multidimensional space having three or more dimensions. The apparatus includes:

a device for displaying in a first display region a selected predefined portion of an electronic publication formed from predefined portions of text-based data encoded using a markup language, each predefined portion having at least one attribute being a coordinate of an axis of the multidimensional space, wherein logical connections among the predefined portions, and any logical connections between the predefined portions and predefined portions of any further electronic publication data in the multidimensional space, correspond to one or more axes of the multidimensional space;

a device for displaying a point on a selected axis of the multidimensional space dependent upon an attribute of the displayed predefined portion;

a device for displaying a second point on a second, viewing axis orthogonal to the selected axis, the second point being derived from the first axis at the first point dependent upon a logical connection between the displayed predefined portion and a predefined portion associated with the second point; and

a device for displaying information regarding the second point of the second axis in a second display region, the first and second points being displayed in two display regions.

According to a fourth aspect of the invention, there is provided an apparatus for navigating in a multidimensional space having three or more dimensions, the multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The apparatus includes:

a device for providing a view comprising at least two anchor sets;

a device for displaying at least one base point and at least a first axis depending from said base point;

a device for displaying at least one of a further point and an axis derived from the base point;

a device for navigating a multidimensional space formed by the points and axes;

a device for returning to the base point when required; and

a device for adjusting the view so a current view point becomes a new base point.

According to a fifth aspect of the invention, there is provided a computer program product having a computer readable medium having a computer program recorded therein for navigating in a multidimensional space having three or more dimensions. The computer program product includes:

a computer program code module for displaying in a first display region a selected predefined portion of an electronic publication formed from predefined portions of text-based data encoded using a markup language, each predefined portion having at least one attribute being a coordinate of an axis of the multidimensional space, wherein logical connections among the predefined portions, and any logical connections between the predefined portions and predefined portions of any further electronic publication data in the multidimensional space, correspond to one or more axes of the multidimensional space;

a computer program code module for displaying a point on a primary axis of the multidimensional space dependent upon an attribute of the displayed predefined portion;

a computer program module for displaying a second point on a second, viewing axis orthogonal to the first axis, the second point being derived from the first point dependent upon a logical connection between the displayed predefined portion and a predefined portion associated with the second point; and

a computer program code module for displaying information regarding the second point of the second axis in a second display region, the first and second points being displayed in two display regions.

According to a sixth aspect of the invention, there is provided a computer program product having a computer readable medium having a computer program recorded therein for navigating in a multidimensional space having three or more dimensions, the multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The computer program product includes:

a computer program code module for providing a view comprising at least two anchor sets;

a computer program code module for displaying at least one base point and at least a first axis depending from said base point;

a computer program code module for displaying other points, axes or both derived from said base point;

a computer program code module for navigating a multidimensional space formed by said points and axes;

a computer program code module for returning to said base point when required; and

a computer program code module for adjusting the view so a current view point becomes a new base point.

According to a seventh aspect of the invention, there is provided a method of publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The method includes the steps of:

storing predefined portions in terminal nodes; and

providing one or more higher level nodes for organising the terminal nodes to correspond with a hierarchical structure embodied in the electronic publication, wherein each higher level node consists of the identity of a parent node, a position indicator for the higher level node, and an identifier;

wherein one of the higher level nodes has a null parent identity, and the position indicator indicates a position of the higher level node relative to a sibling node.

According to an eighth aspect of the invention, there is provided an apparatus for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The apparatus includes:

a device for storing predefined portions in terminal nodes; and

a device for providing one or more higher level nodes for organising the terminal nodes to correspond with a hierarchical structure embodied in the electronic publication, wherein each higher level node consists of the identity of a parent node, a position indicator for the higher level node, and an identifier;

wherein one of the higher level nodes has a null parent identity, and the position indicator indicates a position of the higher level node relative to a sibling node.

According to a ninth aspect of the invention, there is provided a computer program product having a computer readable medium having a computer program recorded therein for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The computer program product includes:

a computer program code module for storing predefined portions in terminal nodes; and

a computer program code module for providing one or more higher level nodes for organising the terminal nodes to correspond with a hierarchical structure embodied in the electronic publication, wherein each higher level node consists of the identity of a parent node, a position indicator for said higher level node, and an identifier;

wherein one of the higher level nodes has a null parent identity, and the position indicator indicates a position of the higher level node relative to a sibling node.

According to a tenth aspect of the invention, there is provided a method of publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language. The method includes the steps of:

storing predefined portions in terminal nodes; and

providing one or more higher level nodes for organising the terminal nodes to correspond with a hierarchical structure embodied in the electronic publication, wherein each higher level node consists of the identity of a parent node, a position indicator for the higher level node, and an identifier, the predefined portion includes text associated with a commentary, and a scope including a start date, an end date and an update date, the update date being later than the start date and earlier than the end date;

further wherein one of the higher level nodes has a null parent identity, and the position indicator indicates a position of the higher level node relative to a sibling node.

Other aspects of the invention are also disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

A small number of embodiments of the invention are described with reference to the drawings, in which:

FIG. 1 illustrates a grid of a multidimensional space according to the first embodiment;

FIG. 2 illustrates the effect of the various axes;

FIG. 3 illustrates the mapping of various axis intersection points, or nodes, that is used to organize, present, and find information (present and past) according to the first embodiment;

FIG. 4 illustrates the application of legal information to mapped nodes according to the first embodiment;

FIG. 5 is a block diagram illustrating a general purpose computer that can be used to implement the electronic publishing system according to the first embodiment;

FIG. 6 is a flow diagram illustrating the method of electronic publishing according to the first embodiment; and

FIGS. 7 to 17 are screen shots illustrating operation of the first embodiment as a software application executing on a general purpose computer.

One or more embodiments of the present invention are described hereinafter with reference to the drawings, in which:

FIG. 18 is a screen shot of a Normal axis view of a MALT publication (with a search mode enabled) in accordance with an embodiment of the present invention;

FIG. 19 is a screen shot of a Versions axis view of a MALT publication in accordance with an embodiment of the present invention;

FIG. 20 is a screen shot of a Source axis view of a MALT publication in accordance with an embodiment of the present invention;

FIG. 21 is a block diagram representation of higher level scoping in accordance with an embodiment of the present invention;

FIGS. 22A, 22B and 22C are screen shots illustrating a commentary in accordance with a further embodiment of the invention; and

FIG. 23 is a computer program product block diagram.

DETAILED DESCRIPTION

The present invention is directed towards a system of electronic publishing that can overcome the disadvantages of conventional information publishing, both in print and electronic form. The present invention reduces, if not eliminates, end user problems with conventional information publishing including:

-   -   (1) the connectivity between related pieces of information;     -   (2) analysis of the type and subject of information; and     -   (3) finding information appropriate to the point in time with         which they are concerned.         Overview of Embodiments

The embodiments of the invention provide an entirely new way of delivering, storing and publishing information. The embodiments allow publishers to add an arbitrary number of logical connections to a set of data, and even permit the publisher to display the precise evolution of that data set over time. This can be done without getting bogged down in the complexity of the logical connections and without limit as to storage space.

Frequently, people desire to have more “information” available. However, with the advent of the Internet and new technology, many people suffer from information overload. The embodiments of the invention provide an easy and effective way to navigate large complex volumes of information.

Conventionally, information may only contain very rudimentary (i.e., haphazard hyperlinks) or non existent logical connections. Thus, conventional techniques of investigating how a set of data has evolved and changed over time can only be done for small data sets and are very expensive.

However, with the embodiments of the invention, it is possible to list all logical connections within a data set no matter how complex those connections may be. The embodiments of the invention and the principles of those embodiments described hereinafter can be applied to many different types of information such as medical, scientific, pharmaceutical, etc. For ease of description, however, the embodiments are set forth in relation to legal information.

Conventionally, legislation is often purchased in two ways: (1) The individual Numbered Acts and Regulations that give each piece of legislation as it is passed; and (2) Consolidated legislation that provides the latest consolidated version.

In the embodiments of the invention, legislation is stored using every version of each Act or Regulation. The end user can search every version of any section, schedule, or provision. For example, the required version of a section is immediately available as is the opportunity to view every preceeding and subsequent version of the same section. Also, links are available to any relevant amending legislation commencing that change, as well as the one that repealed it. Relevant Application, Saving or Transitional Provisions can also be easily accessed.

In this manner, it is possible to come to a full understanding of the legislation just by looking at the data provided through the embodiments of the invention. In contrast, using conventional techniques, it would have been impossible or very hard, expensive and time consuming to do so.

Using conventional means, a person wishing to view a particular section of a particular Act (e.g., the Income Tax Assessment Act) as of a particular date (e.g., 30 Jun. 1996), a significant amount of work would be required to do so. The end user would need to track all Amendments since the last reprint of the legislation, which may take a long time and involve referring to many volumes. This may even possibly involve using scissors and paste to actually cut and replace words. Even to figure out which Acts amended a particular section and to trace those commencement dates can be difficult, time consuming and trying. However, a piece of research that may have taken an experienced researcher days or even weeks can be accomplished in minutes using the embodiments of the invention.

The ability to move through information in time is outlined above. The embodiments of the invention also give additional flexibility and SCOPE to the end user. Further dimensions and interconnections may include: type, jurisdiction, subject, depth. Some examples are:

-   -   1. Doing research on the subject evidence at depth confession         for types Acts and Case for time period 12 months.     -   2. Doing research on type cases within jurisdictions NSW and         Queensland subject murder and depth statutes dealing with         subject.

The ability to associate the relevance and interconnection contained within the information is highly advantageous to the end user.

A key aspect of the embodiments of the invention in successfully providing a multi-dimensional repository of information has been in deciding the “optimum storage unit”. In the past publishers have chosen to either store new versions of the entire Act (too big) or new versions of each and every change, in a method similar to red lining (too complex). The first aspect of the invention was to analysis the data and choose to store every version of every section or provision level of legislation.

Structured Generalised Markup Language (SGML) is a recognised way to mark up data. SGML allows logical structure to be added to a document (unlike HTML and word processors which only allow the addition of visual content). SGML alone is not enough to deal with text-based data that contains a highly complex logical structure. The complexity increases exponentially until the complexity cannot be managed any more. Large legal publishers have stored their data in SGML, but those legal publishers that are successful in dealing with their SGML-based data have purposely kept their markup as simple as possible. When such publishers have tried to encode a complex structure on text-based data their costs of creating the data set and maintaining the data set simply went through the roof, and it became impossible to maintain the integrity of the data set.

In contrast, the embodiments of the invention allow SGML data to be encoded with a much more complex structure whilst remaining manageable. Alternatively, Extensible Markup Language (XML) may be used. For example, with SGML it is possible to encode all 71 versions of Section 6 of the Australian Federal Income Tax Assessment Act in a single file (that Act has about 6,000 sections) but this would be utterly unmanageable when applied to the 6,000 other sections of the Income Tax Assessment Act. It becomes even more unmanageable if anybody would try to use the above method on all the sections within all other Acts and Regulations of the Commonwealth. A significant problem with using SGML, even well executed SGML, is that it is possible to quickly get bogged down in unmanageable levels of complexity. The embodiments of the invention have overcome these problems.

Another key aspect of the invention is the use of database technologies in the management of the SGML encoded techniques. Database technology provides a large number of ready tools to deal with complex structured data. The embodiments combine these technologies (SGML, XML and database technologies) in an advantageous manner.

In the past, traditional publishers have been limited by the size and speed of available storage systems. Only a limited amount can be reproduced in paper and until recently hard disk costs prohibited the storing of multiple gigabytes of data, for both publishers and clients alike.

The embodiments of the invention have the ability to look at situations from a new and up-to-date view point and therefore come up with innovative conclusions that can be radically different to processes employed in the past.

Thus, the embodiments of the invention provide a new computer publishing system that changes the availability of electronic information from being merely “speeded up paper” to being electronic information taking advantage of new electronic media by providing users with enhanced functionality of data retrieval and manipulation. The information included in the electronic format is of a publishable standard, meets cost constraints and is able to be accessed under any combination of dimensions from the multi-dimensional space (Acts, cases, time, jurisdiction, subject). The publishing system facilitates continual updates to the data contained in the databases, without any adverse effects on the operating capabilities that make the publishing system unique. Due to the extra functionality, the publishing system is also designed in such a way that it can still be made available in as many different electronic media as possible, and all search functions are able to operate in a time-efficient manner.

The embodiments of the invention organize, process and present information in a way that is significantly different than conventional structures, processes and presentation. They provide an information storage and publishing system, and in particular, an information storage and publishing system that stores and manages large and comprehensive amounts of information (eg, legal information).

Publication data, being preferably legal information, is encoded using Standard Generalized Markup Language (SGML) or Extensible Markup Language (XML) which adds codes to the publication data and provides functionality to the data. The publication data is processed as a plurality of predefined portions, which in the case of legislation is preferably at the section, schedule level, or provision level. A hierarchy of divisions of the legislation may be implemented. For each of the predefined portions, the system stores a copy of the predefined portion and a modified predefined portion in the first database whenever it is changed. A second (relational) database is preferably provided that comprises plural attributes for managing the information of the first database, with each attribute being a point on an axis of a multidimensional space for organising the data for publication. Alternatively, a single repository of information may be practised as described with reference to the second embodiment.

The system enables the first database to be searched for one of the predefined portions of the publication data using attributes of the second database by following one or more pathways through the multidimensional space. The plurality of attributes are connected to by the plurality of links. Once the desired predefined portion is located, the predefined portions can be retrieved using the attributes to define a point in the multidimensional space.

Preferably, the system implements, inter alia, time-based legislation in which sections of legislation that have been amended are not discarded and replaced with the current provision only as of the publication date. Instead, each version of an amended section is retained in the first database. Thus, the systems according to the embodiments of the invention are particularly advantageous in that legal information is published so that a user can obtain such sections or provisions at a particular time point.

The embodiments advantageously divide information into “suitably” small pieces (or blocks) of text, each of which is a predefined portion of data, and add to each piece of text, either expressly or implicitly, a number of attributes (characteristics or descriptors). The suitability as to size of text pieces is determined by an analysis of the information and its naturally occurring structure based on knowledge of how the information is used and consumed by the end user.

This makes it possible to locate each piece or block of text at a particular point in a “multidimensional space” using as coordinates the attributes added to the piece or block of text. Multidimensional space refers to an area not having boundaries and that is capable of, or involves, more than three dimensions.

FIG. 1 illustrates a multi-dimensional space 100 as used in embodiments of the invention. The multidimensional space is represented by a layered grid. The diagram represents axes or pathways as vertical and horizontal lines; in reality (in the case of more than two dimensions), they are at all angles and inclines.

Referring to FIG. 2, the ability to locate (assign) or map each node 102 (or key intersection point of the various axes or pathways) is a significant functional aspect of the embodiments of the invention. This mapping is explained further hereinafter. With such coordinates 102 known (located or mapped), it is possible to move easily between points in the multidimensional space 100.

The effect of mapping nodes as shown in FIG. 3 is that a course 320 through the information represented in the three-dimensional space 100 can be easily plotted. The user begins the course 320 at node 302 and progresses vertically downward to the fourth node 304. Further, the plotted course 320 is flexible to the extent of the relationships a user chooses to follow or seek out.

First Embodiment

A first embodiment of the invention provides information management in the multidimensional space and allows movement along different axes or “pathways”:

location of the information (its address);

type of information (its genesis);

jurisdiction (its class);

subject (its content description);

depth (extent of content); and

time (the point in time at which the information is viewed).

In the first embodiment, coding of information or data for publication is based on SGML or XML and one or more specifically developed Document Type Definitions (DTD), which preferably is specifically designed for legal information. Alternatively, in the case of XML, a Style Sheet Mechanism (SSM) may be used. This coding can then be related back to information retained in a specifically developed database that enables the code information to be managed and updated. For a detailed description of this aspect of the invention, reference is made to Appendix C. The DTDs according to the first embodiment are set forth in detail in Appendix B. A DTD is used to define the structure of publication data, preferably being legislation, down to a comprehensive level. This is done by using information coded in conjunction with any one of a number of off-the-shelf, free-text retrieval software packages (eg, Folio Views or Dynatext) to deliver the information to the end user.

A DTD describes the markup for the SGML publication data, or “repository”, which may contain legislation, case law, journal articles and other types of material that are stored in computer files. The files contain publication data in text form and the markup, which is extra information about the text included with the text. An example of a markup is ‘<BD+>’ which indicates that “the data from this point on is bold”. A further example is

‘<SECTION ID=“CWACT-19950104-SEC-1” LBL=“1”>’. This markup indicates that: the data from this point on is part of a section of legislation; the section has an identifier of CWACT-19950104-SEC-1; and the section has a label of “1”.

There are a number of different ways to add markup to data. The first embodiment adds markup to data using SGML. Alternatively, XML may be used. Still further, in the case of XML being used, an SSM may be used. Even within SGML, there are many ways to add markup to text. Each particular way of adding markup within SGML is described by using a DTD. In the first embodiment, the data for publication is marked up using a number of different DTDs. In particular, the DTDs are used to mark up the logical structure of the legislation, case law or journal articles. Significant amounts of information about the data for publication is stored in the markup. For example, the markup ‘<SECTION ID=“CWACT-19950104-SEC-1” LBL=“1”>’ provides the following information: the data is a piece of Commonwealth of Australia legislation (indicated by ‘CW’ at the beginning of the string); the section is part of an Act (‘ACT’ after ‘CW’) and not a regulation; the act is Act No. 104 of 1995 (‘19950104’ in the middle of the string), the data is a Section (‘SEC’) within the Act; and it is Section 1 (‘1’ at the end).

The preparation of such DTDs necessitates that the author has a sound knowledge of the data that will be marked up using the DTD. It is especially important that the underlying structure of the data to be marked up using the DTD be understood. The process of becoming acquainted with the structure of the data to be marked up is referred to hereinafter as “content analysis”.

In particular, the section-level or schedule-level portion of legislation is used in the first embodiment. That is, the section-level portion is preferably the predefined portion of the publication data, which is the smallest piece of information to be tracked. This is unlike conventional publishing systems. For example, with reference to Table 1, the first embodiment stores every version of Section 6. In this manner, complexity (tracking every word) is reduced by increasing storage. However, unlike example (I) of conventional publishing systems, the first embodiment does not lose any pertinent information:

-   -   a) every version of each Act or Regulation is stored;     -   b) the end user can search every version of any section or         schedule at the same time;     -   c) it is easy to know which particular section or schedule has         changed, to track how that particular section or schedule has         changed, and to find the relevant section of the Amending Act or         Regulation that affected the section or schedule;     -   d) if multiple changes have occurred on a particular section or         schedule, every version of the section or schedule can be seen;     -   e) issues like commencement of the latest version of a         particular section or schedule and so-called “Application,         Saving or Transitional Provisions” can easily be recreated;     -   f) it is possible to come to a full understanding of the         legislation just by looking at the data provided through the         first embodiment.

A further advantage of tracking every version of each section or schedule is that it is possible to store some of the information, not in the markup, but in a database, as noted hereinbefore. This simplifies the updating process.

While SGML is a powerful way of storing information, it is not a retrieval medium. Therefore, the stored information needs to be converted into a format that the end user of the information can access. The first embodiment uses an electronic format for retrieval. For this electronic retrieval, a software application called ‘high-end text retrieval software’ is used. Examples of high-end, text-retrieval software applications include Folio Views and Dynatext. In the first embodiment, Folio Views is used.

Folio Views has its own proprietary markup language, which is not part of the SGML family. A complete guide to the Folio Views markup language is provided in the text Folio Views Infobase Production Kit Utilities Manual, Version 3.1, Provo, Utah: Folio Corporation (1 Jun. 1994). Storing the data for publication in SGML allows other retrieval software applications besides Folio Views to be used.

In the first embodiment, a process is implemented to convert the SGML marked-up data into the format used by the retrieval software application. The example given for Folio Views hereinafter is but one example of the process involved. The conversion program basically maps the SGML markup to Folio Views markup. For example, for the SGML markup ‘<SECTION ID=“CWACT-19950104-SEC-1” LBL=“1”>’, the conversion process marks all ID's substantively unchanged as Jump Destinations (JD's): ‘<JD:=“CWACT-19950104-SEC-1”>’.

A Keying Guide for Australian Legislation Documents with instructions for the conversion process to Folio Views added is provided in Appendix D.

Movement through legal information can be as follows (the flexibility and scope is largely up to the end user):

-   -   (1) doing research on the subject of fences and boundaries at         the depth fences that are hedges looking for types Acts and         Regulations in jurisdictions NSW and Victoria for the time         period last 20 years;     -   (2) doing research on the subject evidence at depth confession         for types Acts and cases for time period last 12 months; or     -   (3) doing research on type cases with jurisdictions NSW and         Queensland, subject murder and depth statutes dealing with         subject.

The application of legal information to mapped nodes is shown in FIG. 4. However, this is only one of numerous possible applications. Information from medical, technical and scientific areas are all open to the application of this invention. This diagram substitutes the technical terminology of FIG. 3 with legal terms to show the way information appears according to the first embodiment. Further, FIG. 4 provides an example of how legal information is navigated by an end user. The user may be seeking information on the following matters:

-   -   (1) Does NSW legislation on fences presently cover hedge rows         between the boundary of a private property and a public road?     -   (2) If not, have such hedge rows ever come under NSW         legislation?     -   (3) Are there any cases under current law or previous law?     -   (4) How have the cases been interpreted?

Some general assumptions are made about legal information for the purposes of this example. Broadly, legal information has two main primary sources: statute law (including subordinate legislation), and case law. There is also secondary information such as commentary which can be added to aid interpretation. Each of these sources is interconnected and relevant to the other in terms of both past and present information. This may also apply to future information in terms of bills or other forms of uncommenced legislation. It is the association of this relevance and interconnection that is advantageous to the end user.

In FIG. 4, the X-, Y-, and Z-axes indicate time (Time), the legislative provision (location), and type (eg, legislation=L, cases=C, and journal articles=J). To simplify the diagram, only three axes are illustrated, however, other axes may be included dependent upon the number of dimensions of the space. In the first embodiment, the multidimensional space also includes another three axes: jurisdiction=U, subject=V, and depth=W. Thus, the space according to the first embodiment has six dimensions. In the six-dimensional case, it is possible to move along each axis and at the points of intersection change direction, as well as find and/or follow new or additional information.

The end user begins at legislation (L) along the Z-axis, where the Fences 10 and Boundaries Act is located and then selects Section 1 of legislation (indicated by L allowing the Z-axis) at node 402, as of 1 Jan. 1996. The user then follows a path in the legislation through nodes 404, 406 and 408 for Sections 2, 3 and 4, respectively, as of that same date (ie, the Y-axis), to find a definition of the term “fences”. Node 408 contains Section 4 at 1 Jan. 1996 which contains the current definition of “fences”. This would provide information in response to above query (1).

The user then selects Section 4 of the legislation as of 1 Jan. 1995, which in this case is an earlier version of the section prior to amendment, by moving to node 410 (along the X-axis). This provides information about the prior law for above query (2). The user can then move to other information on Section 4 as of 1 Jan. 1995 by going to nodes 412 and 414 for case and journal article information, respectively, along the Z-axis. For example, a case on the earlier Section 4 might be identified at node 412 and articles on interpretation of Section 4 at node 414. The foregoing is only one possible route through the multidimensional space of information. Other more complicated and interrelated pathways involving axes U, V and W are possible. For example, the user can move to axis U (jurisdiction) and compare the definition in Section 4 of New South Wales with that in another jurisdiction (eg, Victoria).

FIG. 6 is a flow diagram illustrating the method of electronic publishing according to the first embodiment. A data source 602, preferably for legal information, is provided. In steps 604 and 606, base data and new data are input from the data source 602, respectively, and in step 608 the data is captured. The DTDs 610 are input to step 612. The DTDs 610 include Act.DTD, Acts.DTD, Reg.DTD, Regs.DTD, and Common.ELT, which are shown in detail in Appendix B. In step 612, the DTDs 610 are applied to the captured data from step 608. In step 614, the data is coded in SGML, including the Time Base Code. In step 616, the data is consolidated. As indicated in FIG. 6, steps/items 602 to 616 comprise the (first) data conversion stage.

A data management database 620 is provided to step 618. The database is based on a master table and a textblock table (see Appendix C for further detail). The output of step 616 is also provided to step 618. In step 618, the data is consolidated; the data is stored as multiple versions, if applicable, and uses the predefined portions of data (ie, textblocks). In step 622, a filter program(s) is applied to the consolidated data to convert the data from SGML to the relevant format for the retrieval software application, including Folio Views, DynaText, Topic, HTML, and the like. Steps/item 618 to 622 comprise the (second) data management stage.

The filtered data output by step 622 can then be provided to step 624. In step 624, the filter consolidated data is imported to the text retrieval software. In step 626, the data is provided to the delivery medium, which may include CD-ROM, DVD, magnetic tape, electronic online services, and other media. The output of this is the end user product 628. Steps/item 624 to 628 comprise the (third) product manufacture stage.

The first embodiment is preferably practiced using a conventional general-purpose computer, such as the one shown in FIG. 5, wherein processes for providing and managing the information are carried out using software executing on the computer. In particular, the legislation database, the database and the DTD(s) may be stored after a filtering process on a CD-ROM used by the computer system, and the computer system is operated using Folio View. The computer system 500 includes a computer 502, a video display 516, and input devices 518. A number of output devices, including line printers, laser printers, plotters, and other reproduction devices, can be connected to the computer 502. Further, the computer system 500 can be connected to one or more other computers using an appropriate communication channel such as a modem communications path, a computer network, or the like.

The computer 502 consists of a central processing unit 504 (simply, processor hereinafter), an input/output interface 508, a video interface 510, a memory 506 which can include random access memory (RAM) and read-only memory (ROM), and one or more storage devices generally represented by a block 512 in FIG. 5. The storage device(s) 512 can consist of one or more of the following: a floppy disc, a hard disc drive, a magneto-optical disc drive, CD-ROM or any other of a number of non-volatile storage devices well known to those skilled in the art. Each of the components 504 to 512 is typically connected to one or more of the other devices via a bus 514 that in turn can consist of data, address, and control buses.

The video interface 510 is connected to the video display 516 and provides video signals from the computer 502 for display on the video display 516. User input to operate the computer 502 can be provided by one or more input devices. For example, a operator can use the keyboard 518 and/or a pointing device such as the mouse to provide input to time computer 502. Exemplary computers on which the embodiment can be practiced include Macintosh personal computers, Sun SparcStations, and IBM-PC/ATs and compatibles.

In an alternate embodiment of the invention, the computer system 500 can be connected in a networked environment by means of an appropriate communications channel. For example, a local area network could be accessed by means of an appropriate network adaptor (not shown) connected to the computer, or the Internet or an Intranet could be accessed by means of a modem connected to the I/O interface or an ISDN card connected to the computer 502 by the bus 514. In such a networked configuration, the electronic publishing system can be implemented partially on the user's computer 500 and a remote computer (not shown) coupled over the network. The legislation database, the database and the DTD(s) can be implemented on the remote computer and the computer system 500 can be operated using Folio View.

The operation of the first embodiment is described with reference to the screen shots shown in FIGS. 7 to 17. All screen shots are derived from the first embodiment which uses Folio Views as the retrieval software. Broadly, FIGS. 7 to 15 are screen shots illustrating navigation or movement around the information. FIGS. 16 and 17 are screen shots that show search capacities.

FIG. 7 shows the opening screen 700, which the end user sees when the program is started. The interface is a standard windows interface featuring drop menus that provide access to all functions. The functions include basic searching and customised search templates such as the ones shown in FIGS. 16 and 17 that allow users to exploit time-based and multidimensional searching.

The title screen 702 is presented when the process is commenced and is the first screen. A customisable toolbar 704 is provided for searching functions. Also, drop menus 706 are provided above the toolbar 704. In the lower portion of the screen 700 contains a status bar 708 showing information relevant to searching. The Start and Main menu buttons 710 in FIG. 7 are both navigational tools. The Start button takes a new user to information providing help on how to use the invention. The Main Menu button takes the end user to the menu shown in the second screen shot of FIG. 8.

FIG. 8 shows a main selection menu 800. At this menu 800, the user can see the currency of the total information. The user is also able to make broad choices as to the type of information that the person might like to see. All items preceded by bullet points in the menu are jump links 802 which lead the user to further menus for the items selected. The jump links 802 also provide a uniform or consistent form of movement. Thus, if searching the Social Security Act, selecting the first jump link “Find an Act” takes the user to the next screen which would be the “Act Name Menu”.

FIG. 9 shows the “Act Name Menu” screen 900. In this menu 900, all letter buttons are links 904 to Acts beginning with the letter selected. That is, the jump links 904 allow access to sub-menus for Acts with the corresponding selected letter. If “S” is clicked, this leads to the “Acts beginning with S” menu (see FIG. 10) where an entry linked to the most current version of the Social Security Act 1991 appears. A similar menu may be provided for Regulations. Further, locational information 902 is provided in the upper portion of the screen 900.

FIG. 10 illustrates acts beginning with “S”, as selected in the screen 900 of FIG. 9. By selecting jump link 1002, the Social Security Act can be accessed. Likewise, other acts in this screen 1000 may be accessed using the respective jump link (e.g. Safety, Rehabilitation and Compensation Act.

Assuming the appropriate jump link 1002 is selected in FIG. 10, FIG. 11 shows how the beginning of the Social Security Act appears in screen 1100, and the buttons that link the user to the provisions of the Act. This is the start of the most current version of the Social Security Act preferably. From this screen, provisions of the Act can be accessed. By accessing the Table of Provisions box, the Table of Provisions menu can be accessed. FIG. 12 shows the Table of Provisions screen 1200, and illustrates how a specific provision, say Section 4, can be accessed again using links 1206. Different sections of the Act (e.g. ss 3, 4 and 6A) may be accessed as well using corresponding jump links. Again, location information 1202 is provided in the upper portion of the screen. A return button 1204 is also provided that provides access back to the beginning of the Act.

FIG. 13 shows screen 1300 containing the Time Base Toolbar 1302, which preferably provides eight buttons for accessing time based information. This Toolbar 1302 is not a feature of Folio Views, but is a designed addition added to Folio Views by the first embodiment. It is made possible by the way in which the publication data is coded. The Section Information button 1304 takes the user to an overview of information. The Previous, Next and All buttons 1306 allows the user to have access to the previous, next and all versions of the relevant section. The Subject, Jurisdiction and Related Info buttons 1308 allow the user to view and access sections dealing with a similar subject, or similar sections in other jurisdictions, or related information such as cases and articles on or about the section. This Toolbar 1302 allows a user to cycle through previous and subsequent versions of sections and as shown in screens in FIGS. 14 and 15 to refer to the text of sections amending the section. As well, the user can also call to the screen all versions of the section as one view (or display) using the “ALL” button.

FIG. 14 illustrates a screen 1400 which appears when the user selects the Section information button 1402 (button 1304 in FIG. 13). The resulting popup screen illustrates the time period or date range 1404 covered by this version of section 4. It also indicates the Year and Number jump link 1406 to text of the amending act which created this version of section 4.

FIG. 15 illustrates a screen 1500 which appears when the user selects the previous button 1502 (not shown—it is located behind the popup screen), which corresponds to previous button 1306 of FIG. 13. This shows an earlier version of section 4 that the user can access by using the previous button 1502. The pop-up screen indicates that this version covers a different time span than that shown in FIG. 14.

The screen shots in FIGS. 7 to 15 display a step-through or navigation-based way of locating information. There is also the more direct approach of searching for terms using text retrieval. The screen shots in FIGS. 16 and 17 illustrate such searching provided by the first embodiment. Screen 1600 shown in FIG. 16 provides a customised search template 1602 that includes a time base option allowing a user to search for versions of a section, for example. Screen 1700 shown in FIG. 17 illustrates a customised search template 1702 for case law which includes a time base option connecting cases to legislation at a particular date, for example. Again, the ability to relate such to time and then to mix and match types of information from different sources (jurisdictions) is a feature provided by the coding technique used for the data and not the Folio Views software used to deliver the data to the end user.

Second Embodiment

The second embodiment stores all the information in a single repository which is marked up in SGML or XML. The information is divided in that repository into suitable pieces or blocks of text (as described in the first embodiment) and any relevant markup marks up a whole suitable piece or block of text by (a) choosing suitable pieces or blocks of text, and (b) demanding that relevant markup belongs to a whole suitable piece or block of text, the following becomes possible. A relational database consisting of records consisting of fields can be created with one and only one record per suitable piece or block of text where the actual text of each suitable piece or block of text is the content of one filed of the above record and where each item of the markup is assigned its own field in the above record.

For example, a version of Section 6 of the Income Tax Assessment Act (ITAA) 1936 may be stored as a record in the above relational database, The first field of that record contains the actual text of that version of Section 6. The next field identifies it as Section 6 of the ITAA, the next field gives the date this version came into being, the next field contains the section of the amending act that created this particular version, the next field contains the day this version became superseded, another field contains the subject(s) this version addresses, another field contains the case(s) that have addressed this version of section 6 and so on. Storing the data in this way allows multidimensional database techniques to be applied to the data.

An XML DTD for implementing the second embodiment is set forth in Appendix E. It will be apparent to one skilled in the art that the second embodiment may be readily implemented in view of the foregoing description of the first embodiment, which is not repeated here for the purpose of brevity, and in view of the accompanying DTD set out in Appendix E.

The foregoing only describes a small number of embodiments of the invention, and modifications and changes apparent to those skilled in the art can be made thereto without departing from the scope and spirit of the invention. For example, the embodiments of the invention have been described with reference to SGML. The embodiments may alternatively be practiced with the extensible markup language (XML) as well. Also, the embodiments may alternatively be practiced with a Style Sheet Mechanism (SSM) instead of, or in addition to, one or more DTDs.

A method, apparatus and computer program product for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language are disclosed. In the following description, numerous specific details are set forth. However, it will be apparent to those skilled in the art in view of this disclosure that changes may be made without departing from the scope and spirit of the invention. In other instances, well known features have not been described in detail so as not to obscure the invention. Whilst the invention may be preferably practised on flat files, it will be apparent to a person skilled in the art that the invention may also be practised on databases. A database may be constructed from sets of flat file records. A relational database is a collection of related tables, each table being a set of flat files having the same structure. The method includes the step of: displaying a selected one of the predefined portions in a first display region. The display region preferably takes the form of an area of real estate on a computer screen (henceforth referred to as the “content frame”). The method also includes the step of displaying a view into a primary axis of the multidimensional space in which the displayed preferred portion is clearly marked. This second area of the computer screen shall be referred to as the “reference frame”. Each frame has an associated “anchor”, which is a title bar clearly indicating the nature of the view currently displayed in the frame. The reference anchor also contains tools for navigating the displayed axis. The method also includes the step of displaying a point on a primary axis of the multidimensional space for the displayed predefined portion.

The method may be enhanced by displaying a second point on a second axis which relates to the first axis at the first point. The second axis represents time-based versions of the selected one of the predefined portions. Alternatively, the second axis represents amending legislation that was applied to the selected one of the predefined portions. In another example, the second axis represents case law that applied the selected one of the predefined portions. In further example, the second axis represents annotations to the selected one of the predefined portions. In a yet further example, the second axis represents entries of a subject index that are covered in the selected one of the predefined portions.

The embodiment of the present invention allows for a primary axis (the combined hierarchical/sequential or normal axis). A “base node” may be selected by navigating the primary axis. The method then allows for one of a number of potential axes (associated with the base node) to be selected and subsequently navigated. The selection is accomplished by means of activating “links” in the displayed base node. The reference frame is redrawn to give a view of the members of the selected axis and one member of that axis is displayed. At any point it is possible to return to the primary axis and select a new base node. Alternatively, the currently displayed base node may be chosen as a new base node from which subsequent axes are derived. In this manner, any number of axes may be displayed and navigated without increasing the complexity of the screen view (i.e. only two frames are ever required). It is this quality which allows a complex dataset to be navigated by a non-specialist end user.

By way of example, a user may select a first node, corresponding to a provision, in the multidimensional space. The first node's locator is displayed in a first anchor to provide the user with a first point of reference. If the user is interested in different versions of the provision, the user may then move to second node on an orthogonal axis, being the Versions axis. The first anchor is updated and displays the locator of the second node. A second anchor displays the locator of the first node. The second anchor also displays the relationship between the first node and the second node. The user is provided with information which indicates the original provision that was being studied, the provision currently being studied and the current provision's relationship to the original provision. Thus, the first and second anchors and the information provided therein enable the user to navigate the multidimensional space.

Where reference is made in any one or more of the accompanying drawings to steps and/or features, which have the same reference numerals, those steps and/or features have for the purposes of this description the same function(s) or operation(s), unless the contrary intention appears.

The principles of the preferred method described herein have general applicability to electronic publishing. However, for ease of explanation, the steps of the preferred method are described with reference to navigating in a MALT publication. However, it is not intended that the present invention be limited to the described method. It will be appreciated by those skilled in the art that a publication could include a document or a database. The invention may apply to any hierarchical XML data where any of the nodes may change independently of other nodes in the hierarchy. Typical examples might include manuals and newspapers. For example, the invention may have application to the production and display of aircraft manuals. In this case, each node would be a set of maintenance instructions for a part or assembly. The axes might be part number; category (electrical, structural, etc.); location (Boeing 737, wing, wingtip assembly, eddy baffle, securing flange AX-703); airline (United, QANTAS); language (English, French). Since each commercial aircraft is in effect a one-off construct, the basic information needs to be reconfigured for each plane, each airline, etc.

Before proceeding with a description of the embodiments, a brief review of terminology is discussed hereinafter. A dataset refers to the complete set of data that is to be navigated. A dataset has a complete set of discrete objects called nodes. The dataset may be viewed as a sparse multidimensional matrix, as is produced using the MALT publishing method. In the example of this specification, the dataset preferably refers to a body of legislation designed for point in time searching.

A node preferably corresponds to a particular legislative provision at a particular date. A base node is a particular node from which one or more viewing axes may be derived.

A viewing axis is an ordered set of nodes derived from a single base node. The base node itself may or may not constitute part of the axis. For example, given a particular provision in time, three possible viewing axes are: the set of all provisions in force on the same date as the base node; the set of versions of the base provision in time; and the set of amending provisions most recently applied to the base provision. Further viewing axes may be practised, and may include case law that applied the provision, annotations to the provision and entries of a subject index that are covered in the provision.

A provision, for the purposes of this system, is a unit of legislation having a heading and/or content, but not including text belonging to any sub-provision that is a predefined portion of text. A provision may be an Act, a schedule, a chapter, a section or other legislative unit. A provision has a scope in time, such that when a provision is amended, a new provision is created. A provision corresponds to a set of nodes, each node corresponding to a range of dates in the scope of the provision.

Scope refers to a period of time during which a provision is in force. Thus, a given scope is usually expressed as start and end dates. A provision's scope is determined by the dates on which the provision commenced, was amended and/or was repealed.

A locator is an identifier that is used to locate a particular node. For example, a locator may be a date, or a position such as the name of an Act and a section number.

Multi-axis Viewing Interface

Using the publication of legislation as an example, a provision is defined as being an amendable unit of legislation. At any given moment, the body of active legislation can be divided into provisions. Provisions also have a scope in time, so that when a provision is amended, the current provision goes out of scope and a new provision is created. The nodes of the dataset in this example are provisions with an associated date. Two locators are required to specify a particular node uniquely: a position (such as act and section number) and a date.

There are a number of viewing axes associated with each node. As indicated in the explanation of terminology above, a viewing axis is defined as an ordered set of nodes that can be derived from the current node. When XML data is converted to a series of flat files, viewing axes are derived from the current node as a result of an intersection between two flat files. Two flat files intersect if common entries are contained in the fields of the respective flat files. For example, a legislation flat file may contain a field “Identifiers of cases that apply this provision”. The legislation flat file shares a common entry with a case law flat file. Alternatively, the legislation flat file may contain a field “subjects covered in the provision”. In this example, the legislation flat file shares a common entry with a subject index flat file. Alternatively, an amending legislation flat file may have a field “Identifiers of provisions amended by this provision” and share a common entry with the legislation flat file.

In a preferred example, seven such viewing axes are:

-   -   Sequential ( . . . ; s 26; s 27; s 27A; . . . ),     -   Hierarchical ( . . . ; Corporations Act 1989; Part 2; Division         2.1; s 27),     -   Temporal (the set of versions of the current provision in time),     -   Source (the set of provisions which amend the current         provision),     -   Case law (cases that apply the current provision),     -   Annotations (annotations to the current provision), and     -   Subject (Entries of a subject index that are covered in the         current provision).         The above axes are orthogonal in the sense that none can be         directly derived from another. Thus, the temporal axis cannot be         derived from the sequential axis. Moreover, members of the         temporal axis are not simply those provisions sharing the same         locator as the current provision. As a result of renumbering,         members of the same temporal axis may possibly have widely         differing locations. While the example uses two locators and         four viewing axes, the MALTweb interface is capable of handling         as many locators and axes as required.

Having utilised MALT to construct a set of data encapsulating the above relationships, the problem is how to access this data in a meaningful way. To provide an untrained user with full multi-axis access to MALT type data whilst maintaining a consistent look and feel throughout, a view consisting of a two frame screen is provided.

FIG. 18 is a screenshot 1800 depicting a section of legislation in accordance with an embodiment of the invention. A content frame 1810 displays the content of the current node. In essence, this frame 1810 constitutes a known portion of display “real estate”. In the example of FIG. 18, the node corresponds to Section 59 of the Commonwealth Corporations Act 1989 and the node has a scope of 16 Oct. 1995 onwards. The scope indicates the time during which the provision is in force. The content anchor 1805 of the content frame 1810 displays the locators for the current content provision in a user friendly form, such as:

Corporations Act 1989 (Cth): s 59 (Scope: 16 Oct. 1995 Onwards)

Situated above the content anchor 1805 is a reference frame 1820, which contains a set of links 1821 corresponding to the members of a viewing axis associated with the current base node. Reference markers 1823 indicate which of the links 1821 is currently selected. In the Normal view, the content node shown in the content frame is always the same as the base node for the reference frame. In the Version view, the content node and base node are initially the same, but deviate when a different version is selected. In the Source view, the base node is being amended and the content node is one of the amending provisions.

The reference frame 1820 has a corresponding reference anchor 1815, which describes the current viewing axis and provides buttons 1816, 1818 for navigating the sequential axis and button 1817 for accessing higher levels of the hierarchy. These levels can also be accessed via the links 1821 in the reference frame. In the example, the reference anchor 1815 indicates that the user is being shown a normal view of s59, as in force on 20 Jul. 2000. This view also shows the search mode, in which the text “exercise of jurisdiction” has been located. The buttons 1812, 1813 allow access to the next or previous occurrence of this text, whilst button 1814 cancels the search. The “hits” links 1822 in the reference frame allow rapid access to occurrences of the search text in other parts of the document. In this respect, the search mode acts very much like a separate viewing axis. The highlighting 1806 indicates the selected text. Finally, the links 1807, 1808 allow access to the other viewing axes (in this case, Versions and Amendments).

Where appropriate, the reference anchor 1815 may indicate the base node of the viewing axis. The base node is the node from which the viewing axis is derived. For example, the reference anchor 2015 of FIG. 20, which shows a Source axis view of the same provision depicted in FIG. 18, displays the following information:

Provisions Amending (Effective 16 Oct. 1995) Corporations Act 1989 (Cth): s 59

This indicates that the Source axis being viewed by the user is derived from the base provision: Corporations Act, s59 [16 Oct. 1995 onwards]. The content anchor 2005 details the amending provision, which in this example is Corporations Legislation Amdt Act 1994 (Cth):Sch 1.

The relationship of the base node and the content node depends on the view. In the Normal axis view, consisting of the sequential and hierarchical axes, the base node and the content node are always the same. In the Versions axis view, the base node and the content node may or may not be the same.

A view is, therefore, defined as the display of a particular content node in relation to a specified axis. Each view may be uniquely identified from the following: the current content node, the current viewing axis, and the base node of the viewing axis. To further help the user in distinguishing the different viewing axes, the reference frame links may optionally vary in colour, content and indenting style among the views.

FIG. 19 shows a Version axis view 1900 of the provision depicted in FIG. 18. The content anchor 1905 indicates that the provision being displayed is, in fact, an earlier version of the provision displayed in FIG. 18. Thus, the information shown in the content frame 1910 has a different scope from the information shown in content frame 1810 of FIG. 18. Closer examination of the information of the content frame 1910 and the information of content frame 1910 indicates that amendments have in fact been made between the two versions of the provision.

The reference frame 1920 of FIG. 19 indicates that there are two versions of the provision, a first version with a scope of 1 Jan. 1994 to 15 Oct. 1995 and a second version with a scope of 16 Oct. 1995 to 31 Dec. 2001. Each version of the provision is a distinct node on the Version axis. The reference anchor 1915 indicates that the user is navigating along the Versions axis view of section 59.

FIG. 20 shows a Source axis view 2000 of the provision under consideration. The reference anchor 2015 of FIG. 20 indicates to the user that the material being displayed relates to provisions amending the Corporations Act 1989 (CTH); s 59. The reference frame 2020 indicates that there are three relevant nodes 2021, 2022, 2023 on the source axis. Each node corresponds to a provision which amends the current provision. The amending provisions are not necessarily sequential and may be non-consecutive and/or in different schedules and/or in different Acts. The content anchor 2005 indicates that the current information being shown is Schedule 1, Part 1, Item 15 of the Corporations Legislation Amendment Act 1994, corresponding to the first node 2021 shown in the reference frame 2020. The content of the amending act is displayed in the content frame 2010.

Thus, the multi-access viewing interface provides a user with content and reference components. Anchors uniquely identify the content node by position and date, and the viewing axis by base node and axis type. Furthermore, the reference frame is capable of displaying multiple viewing axes for a given base node, as illustrated in FIGS. 18-20.

Higher Level Scoping

The MALT concept encapsulates the ability to store the contents of a sparse multidimensional matrix in a set of flat file records. As previously defined, the scope of a provision is a time period during which the given provision is in force. A problem arises relating to scoping a record which encompasses a number of lower level records.

Consider as an example legislation marked up for point in time searching. The body of the legislation consists of provisions (or nodes), where each provision is an amendable unit of legislation. For the purposes of this example, each provision possesses the following four properties:

-   -   A single parent, or container provision in which the current         provision resides. [The children of a provision are those         provisions which have the current provision as the parent.]     -   A position within a provision's parent, and (optionally) an         associated locator (eg. the fourth child provision of an Act may         have the locator “Chapter 2A”).     -   A scope in time (i.e. start and end dates).     -   The content of the provision.         The provisions are divided into three classes:     -   A single root node, which has no parent, but from which all         other nodes ultimately descend;     -   A set of terminal nodes, which have no children; and     -   A set of higher level nodes which are neither the root node nor         terminal.         The legislation can then be said to form a tree descending from         the root node and containing the terminal nodes at the ends of         the root node's branches.

The scope of a terminal node is the period of time between the terminal node's start date and end date, inclusive. The root node is deemed to be always in scope. The scope of a node which is neither a terminal node nor a root node is problematic.

For example, a chapter may encompass many sections, but the chapter's actual content, viewed in isolation as a record, is simply the chapter's title, including locator if present, and any notes or other attachments that apply to the chapter as a whole. All other content is contained indirectly via the chapter's descendant provisions, such as parts, sections and the like.

Difficulty arises in determining the scope of the chapter node. In one sense, the scope of the chapter node is the sum of the scopes of the chapter node's descendants. A question then arises if, for example, the chapter's title is altered. The same applies to the case in which the abovementioned notes or other attachments are altered.

One solution is to create a duplicate chapter with the altered title. While effective, this method has some major drawbacks. Firstly, it involves a great deal of unnecessary duplication of material. Since each child provision can have only one parent; new copies of every sub-level have to be made. The scope of both the original and duplicate sublevels then have to be split at the date of the chapter's title change. This in turn requires each sub-level to behave as though amended, even though the amendment only applies to the title of an ancestor level.

A better solution is to create a new terminal sub-level of the chapter which contains just the title and associated text. This sub-level can then be scoped independently of the main level, and other sub-levels are unaffected. The sub-levels retain the same parent as the chapter level itself was not affected by the amendment.

However, this still leaves open the question of what to do with the scope of the chapter level. Clearly a chapter, like any other provision, can be created or repealed. Thus, an amendment such as “repeal Chapter 2A” should end the scope of the chapter level as well as all of the chapter's descendants.

The editors, however, may wish to leave a stub entry to mark the place of the former chapter thus:

Chapter 2A [Repealed]

The scope of the stub clearly lies outside the scope of the chapter. There are three possible solutions:

-   -   allow the [repealed] entry (which stands in place of a normal         title) to live inside the chapter, even though the entry is out         of the chapter's scope;     -   extend the scope of the chapter to encompass the scope of the         stub; or     -   create a new chapter level containing just the stub.         The first option creates significant inefficiencies in the         design, since the scope of a sub-level cannot be assumed to lie         within the scope of the sub-level's parent. The other two         options give rise to potential conflicts between the stub and         possible replacement chapters.

Having delegated the title and other general notes to their own sublevels, all content has effectively been removed from the chapter. However, a chapter level is still required, as removing higher levels makes all terminal nodes direct children of the root. This in turn severely impacts on the usefulness of the data when mapped to a hierarchical form, such as XML.

In addition, a higher level does contain one property, namely one or more locators (“Chapter 2A” in the example). While this property can theoretically be delegated to yet another sub-level, the practical implications are significant. In particular, the locator reflects the ordering of the chapter amongst its siblings. If, for example, an amendment renumbers chapter 2A to chapter 4, this gives rise to the issue of whether the chapter comes before or after chapter 3 in either a flat file or in XML. For this reason, the locator is the sole property preserved by a higher level node throughout the higher level node's scope. If the position is changed, then a new level (and sub-levels) is created.

This still leaves the problem of the scope of a higher level. For example, if Chapter 2A is repealed and a new, unrelated chapter 2A immediately takes the place of the repealed Chapter 2A, a problem is potentially presented as to two overlapping scopes for the same provision. The scope of the original node has to be terminated, otherwise there are two Chapter 2As in scope contemporaneously. The co-existence of two Chapter 2As poses a detrimental impact on the ability to navigate and search the legislation under consideration. In the situation in which the original Chapter 2A has a repeal stub, the original Chapter 2A's scope may overlap the new Chapter 2A, since the stub may continue indefinitely in time. Among many possibilities, a repeal stub may be provided while Chapter 2A does not exist.

Other problems include: repeal or substitution of a higher level node; renumbering/relocation of a higher level node; renaming (without renumbering/relocation) of a higher level node; elevation or demotion of a higher level node within the hierarchy, e.g. changing a part to a chapter or a division to a subdivision; and insertion/removal of an intermediate level heading node, requiring that nodes which follow and are/were, according to their type, inferior to that heading node become/cease to be children of that node.

In order to resolve these problems, the following design rule is applied: Higher level nodes may have neither scope nor content. In other words, a non-terminal node must be a container only. A non-terminal node's only properties are a parent indicator, a position within the parent, and (optionally) a locator. Any content notionally belonging to such a node, such as a chapter title, is assigned to a new (terminal) child node. A (terminal) child node may contain a label, which is preferably a title, but can be or include other data related to the parent node. The new child node preserves the scope of the title, so (for example) a single chapter may possess a number of (temporally disjoint) title nodes.

Higher level scoping has a number of surprising but useful consequences. In particular, a higher level provision is, in itself, not subject to amendment. Thus, an instruction such as “Repeal Chapter 2A” actually terminates the scope of all of Chapter 2A's constituent terminal nodes. The chapter node, having no scope of its own, is unaffected.

Additionally, the previously described problem pertaining to the overlapping scope of the 2A repeal stub disappears. Embodiments of the invention utilise the following approaches. When Chapter 2A is repealed, the associated scope of all terminal nodes within Chapter 2A is terminated. In a first embodiment, a new Chapter 2A is enacted immediately after the original chapter is terminated. The new Chapter 2A has an associated scope commencing on the day after which the original Chapter 2A was repealed. In a second embodiment, a repeal stub is introduced. A repeal stub in the preferred embodiment is a title with an attribute marking this title as being of the type “repeal stub”. The repeal stub has an associated scope with a start date corresponding to the date after which Chapter 2A was repealed. The repeal stub has the Chapter 2A node as a parent. If a new Chapter 2A is later enacted, the scope of the repeal stub is terminated and the scope of the terminal nodes of the new Chapter 2A will begin on the day after the end date of the repeal stub's scope.

Thus, a request “for Chapter 2A on date X” returns a description of Chapter 2A that was valid on that date. In the event that the request is for a date on which the chapter is repealed, the fact that the chapter is not in force, having been repealed on or before that date, will be returned.

A portion of Document Type Definition (DTD) code which is used to enable higher level scoping appears in Tables 2 to 8 below:

TABLE 2 <!-- #########################################################  ENTITY: hlev-id  PURPOSE: Concatenation of the elements that make the Identification of a higher level element. Only to be used for levels in which the <desc> can be MALTed - for levels in which the whole level should be MALTed (ie, section, reg, schedule) and for their sub-levels, use %lev-id;. ########################################################### --> <!ENTITY % hlev-id  “(target*, label?, (desc, %amendments;)*)” >

TABLE 3 <!ELEMENT act  (%hlev-id;,   (%hnote; | %raw;)*,   (longtitle, %amendments;)+,   preamble*,   (chapter* | part* | section*),   (schedule* | include+)*,   hist* ) > <!ATTLIST act  juris    (cth|nsw|vic|qld|sa|wa|tas|act|nt|imp)    #REQUIRED  year    CDATA    #REQUIRED  number    CDATA    #REQUIRED >

TABLE 4 <!ELEMENT regulations  (%hlev-id;,   (%hnote; | %raw;)*,   (chapter* | part* | reg*),   (schedule* | include+)*   ) > <!ATTLIST regulations  juris   (cth|nsw|vic|qld|sa|wa|tas|act|nt|imp)   #REQUIRED  year   CDATA   #REQUIRED  number   CDATA   #REQUIRED > <!ELEMENT chapter  (%hlev-id;,   (%hnote;)*,   (((%secreg;)*, part*) | article+)) > <!ATTLIST chapter  id   CDATA   #IMPLIED  next-id   CDATA   #IMPLIED >

TABLE 5 <!ELEMENT part  (%hlev-id;,   hist*,   (((%secreg;)*, division*) |   (article+ | item+ | clause+) |   (guide+) |   (unconverted+))) > <!ATTLIST part  id    CDATA    #IMPLIED  next-id    CDATA    #IMPLIED >

TABLE 6 <!ELEMENT division  (%hlev-id;,   (p | %hnote;)*,   (((%secreg;)*, subdivn*) |   (clause*, item*))) > <!ATTLIST division  id   CDATA   #IMPLIED  next-id   CDATA   #IMPLIED >

TABLE 7 <!ELEMENT subdivn  (%hlev-id;,   (%hnote;)*,   ((%secreg;)+ | clause+)) > <!ATTLIST subdivn  id   CDATA   #IMPLIED  next-id   CDATA   #IMPLIED >

TABLE 8 <!-- ############################################################  ELEMENT: desc  PURPOSE: Defines the “description” of a level.  ATTRIBUTES:   %date-atts; - defines the start and end dates for this version of the description. ############################################################ --> <!ELEMENT desc  (#PCDATA | %refs; | %effect; | quote)* > <!ATTLIST desc  %date-atts; > The DTD has been altered such that scoping is transferred from the higher level nodes to terminal nodes.

Consider an example consisting of an Act with two chapters, the second chapter containing two sections, as shown by the system 2100 of FIG. 21. A root node 2110 represents the Act. The root node 2110 has no parent, and all other nodes descend from the root node 2110. The first chapter of the Act is represented by a higher level node 2120. As a higher level node, node 2120 has neither scope nor content. Node 2120 has the following properties: a parent, being the Act node 2110; a position within the parent node 2110, being 1; and an optional locator, being “Chapter 1”. Node 2120 has two descendant nodes 2122, 2124. Node 2122 has the following properties: a parent, being the node 2120 identified by its locator “Chapter 1”; a position within the parent node 2120, being 1; an optional locator, being “Chapter 1 Description”; scope, being 1 Jan. 1998 onwards; and content relating to the title or textual description of the first chapter of the Act under consideration. Node 2124 has the following properties: a parent, being the node 2120 identified by its locator “Chapter 1”; a position within the parent node 2120, being 2; an optional locator, being “Chapter 1 Note”; scope, being 1 Jan. 1998 onwards; and content providing general notes or comments pertaining to the first chapter of the Act under consideration.

A second higher level node 2130 represents the second chapter of the Act. Node 2130 has two sections. Node 2130 has the following properties: parent, being the Act node 2110; a position within the parent node 2110, being 2; and an optional locator, being “Chapter 2A”. Node 2130 has five child nodes: 2132, 2134, 2136, 2140 and 2150, each of which is a terminal node in this example. Node 2132 has the properties: parent, being Chapter 2A; a position within the parent, being 1; an optional locator, being “Chapter 2A description”; scope, being 1 Jan. 1998-30 Jun. 1998; and content, being “Company Registration”. Node 2134 has the properties: parent, being Chapter 2A; a position within the parent, being 2; an optional locator, being “Chapter 2A description”; scope, being 1 Jul. 1998 onwards; and content, being “Registering a Company”. Node 2136 has the properties: parent, being Chapter 2A; a position within the parent, being 3; an optional locator, being “Chapter 2A note”; scope; and content. Node 2140 has the properties: parent, being Chapter 2A; a position within the parent, being 4; an optional locator, being “Section 11”; scope; and content. Node 2150 has the properties: parent, being Chapter 2A; a position within the parent, being 5; an optional locator, being “Section 12”; scope; and content.

The different scopes of nodes 2132 and 2134 allow nodes 2132, 2134 to co-exist, without overlapping. Nodes 2132, 2134 may share the same locator, but the combination of locator and scope uniquely identifies the nodes. Nodes 2132, 2134 reflect the amendment of the title of Chapter 2A from “Company Registration” to “Registering a Company”. The scopes of nodes 2132, 2134 indicate that the amendment came into effect on 1 Jul. 1998.

In accordance with a further embodiment, higher level scoping is extended to facilitate commentaries, subject indices and similar material. When considering legislation, any amendment results in the production of a modified portion. However, when considering commentaries, two types of amendment to the commentary are possible. In the first scenario, corresponding to the legislation example, the scope of the current predefined portion of commentary is terminated and a new predefined portion is provided. The new predefined portion has a scope commencing on the day after the expiration of the current predefined portion. In the second possible scenario, the current predefined portion of the commentary is amended without a second predefined portion being created.

The scope of commentary portions is extended to include three dates: a start date, an update date and an end date. Referring to FIG. 22A, a screen shot 2260 shows a commentary. The commentary was created on 1 Jul. 2000, as seen from the amendment bar 2265. The commentary has the following scope properties: start date of 1 Jul. 2000, no update date and no end date. FIG. 22B shows a screen shot 2270 of the commentary of FIG. 22A at a later date. The amendment bar 2275 indicates that the commentary was last updated on 1 Sep. 2000. Thus, the scope of the commentary now has a start date of 1 Jul. 2000, an update date of 1 Sep. 2000 and no end date. FIG. 22C shows a further screen shot 2280 of the commentary of FIGS. 22A and 22B at a yet later date. The amendment bar 2284 indicates that at least one further amendment has been applied to the commentary since the update of 1 Sep. 2000 indicated at 2275 in FIG. 22B. The amendment bar 2285 of FIG. 22C shows that the last update date of the commentary is 1 Oct. 2000. Therefore, the scope properties of the commentary now read: First portion: start date of 1 Jul. 2000, end date of 30 Sep. 2000; Second portion: start date of 1 Oct. 2000, and no end date.

In a further embodiment, XML data may be divided into predefined portions and stored as a collection of flat files. In an example, the flat files take the form of a relational database. There is a one to one correspondence between the XML data and the relational database. The hierarchy of the XML data is expressed via the implementation of higher level scoping. A single record is provided with an identifier and other terminal nodes are provided in which to store the remainder of the information.

The process for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language can be implemented using a computer program product in conjunction with a computer system 2300 as shown in FIG. 23. In particular, the process for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language can be implemented as software, or computer readable program code, executing on the computer system 2300.

Similarly, the process for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language may also be implemented using a computer program product in conjunction with the computer system 2300 shown in FIG. 23.

The computer system 2300 includes a computer 2350, a video display 2310 and input devices 2330, 2332. In addition, the computer system 2300 can have any of a number of other output devices including line printers, laser printers, plotters, and other reproduction devices connected to the computer 2350. The computer system 2300 can be connected to one or more other computers via a communication input/output (I/O) interface 2364 using an appropriate communication channel 2340 such as a modem communications path, an electronic network, or the like. The network may include a local area network (LAN), a wide area network (WAN), an Intranet, and/or the Internet 2320.

The computer 2350 includes the control module 2368, a memory 2370 that may include random access memory (RAM) and read-only memory (ROM), input/output (I/O) interfaces 2364, 2372, a video interface 2360, and one or more storage devices generally represented by the storage device 2362. The control module 2368 is implemented using a central processing unit (CPU) that executes or runs a computer readable program code that performs a particular function or related set of functions.

The video interface 2360 is connected to the video display 2310 and provides video signals from the computer 2350 for display on the video display 2310. User input to operate the computer 2350 can be provided by one or more of the input devices 2330, 2332 via the I/O interface 2372. For example, a user of the computer 2350 can use a keyboard as I/O interface 2330 and/or a pointing device such as a mouse as I/O interface 2332. The keyboard and the mouse provide input to the computer 2350. The storage device 2362 can consist of one or more of the following: a floppy disk, a hard disk drive, a magneto-optical disk drive, CD-ROM, magnetic tape or any other of a number of non-volatile storage devices well known to those skilled in the art. Each of the elements in the computer system 2350 is typically connected to other devices via a bus 2380 that in turn can consist of data, address, and control buses.

The method steps for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language are effected by instructions in the software that are carried out by the computer system 2300. Again, the software may be implemented as one or more modules for implementing the method steps.

In particular, the software may be stored in a computer readable medium, including the storage device 2362 or that is downloaded from a remote location via the interface 2364 and communications channel 2340 from the Internet 2320 or another network location or site. The computer system 2300 includes the computer readable medium having such software or program code recorded such that instructions of the software or the program code can be carried out. The use of the computer system 2300 preferably effects advantageous apparatuses for navigating a multidimensional space containing an electronic publication formed from predefined portions of text based data encoded using a markup language and for publishing an electronic publication formed from predefined portions of text based data encoded using a markup language in accordance with the embodiments of the invention.

The computer system 2300 is provided for illustrative purposes and other configurations can be employed without departing from the scope and spirit of the invention. The foregoing is merely an example of the types of computers or computer systems with which the embodiments of the invention may be practised. Typically, the processes of the embodiments are resident as software or a computer readable program code recorded on a hard disk drive as the computer readable medium, and read and controlled using the control module 2368. Intermediate storage of the program code and any data including entities, tickets, and the like may be accomplished using the memory 2370, possibly in concert with the storage device 2362.

In some instances, the program may be supplied to the user encoded on a CD-ROM or a floppy disk (both generally depicted by the storage device 2362), or alternatively could be read by the user from the network via a modem device connected to the computer 2350. Still further, the computer system 2300 can load the software from other computer readable media. This may include magnetic tape, a ROM or integrated circuit, a magneto-optical disk, a radio or infra-red transmission channel between the computer and another device, a computer readable card such as a PC card, and the Internet 2320 and Intranets including email transmissions and information recorded on Internet sites and the like. The foregoing are merely examples of relevant computer readable media. Other computer readable media may be practised without departing from the scope and spirit of the invention.

The process for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language can be realised in a centralised fashion in one computer system 2300, or in a distributed fashion where different elements are spread across several interconnected computer systems.

The process for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language may also be implemented using a computer program product in conjunction with the computer system 2300 of FIG. 23 in a manner similar to that which has just been described.

Computer program modules or computer program in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation or b) reproduction in a different material form.

In the foregoing manner, a method, an apparatus, and a computer program product for navigating in a multidimensional space containing an electronic publication formed from predefined portions of text-based data encoded using a markup language are disclosed. Further, a method, an apparatus, and a computer program product for publishing an electronic publication formed from predefined portions of text-based data encoded using a markup language are disclosed. While only a small number of embodiments are described, it will be apparent to those skilled in the art in view of this disclosure that numerous changes and/or modifications can be made without departing from the scope and spirit of the invention.

Appendix A

-   Example Research -   Social Security Act 1991 No 46 -   Updated as at 9 Aug. 1996     A 1. Amendments to Section at Sep. 8, 1996 -   S.4 am. Nos. 74, 116and 194, 1991; No. 81,1992; No. 36, 1993; Nos.     55, 63 and 184, 1994; Nos. 104 and 105, 1995     A 2. Amendments to Section at Oct. 7, 1995 -   S.4 am. Nos. 74, 116 and 194, 1991; No. 81, 1992; No, 36, 1993; Nos.     55, 63 and 184, 1994     B. Commencement Information for Act No 105 of 1995 contained in     Reprint

Social Security(Non-Budget Measures) Legislation Amendment Act 1995 Date of Number Year Assent Commencement 105 1995 29 Sep. 1995 Subdiv. A of Div. 2 of Part 2 (s. 4): 1 Jul. 1993 Ss. 8 and 9: 1 Jul. 1995 S. 10: 1 Apr. 1993 Div. 5 of Part 2 (ss. 12 and 13): 20 Sep. 1994 (ze) Ss. 17(c), (d) and 18: 1 Jan. 1996 Div. 15 of Part 2 (s. 37): 29 Nov. 1993 Div. 18 of Part 2 (ss. 41-48): 20 Mar. 1995 S. 49 (a): 12 Mar. 1992 S. 49 (b): 1 Jul. 1992 S. 49(c): 28 Jan. 1993 S. 49(d): 1 Mar. 1993 S. 49(e): 24 Dec. 1993 S. 49(f): 1 Jan. 1994 Remainder: Royal Assent C 1. Text of Section at Sep. 8, 1996

-   bold text indicates amendments made by NO 105 of 1995. -   SECT 4     Family Relationships Definitions—Couples -   4. (1) (1) In this Act, unless the contrary intention appears:     -   “approved respite care” has the meaning given by subsection (9);     -   “armed services widow” means a woman who was the partner of:     -   (a) a person who was a veteran for the purposes of any         provisions of the Veterans' Entitlements Act; or     -   (b) a person who was a member of the forces for the purposes of         Part IV of that Act: or     -   (c) a person who was a member of a peacekeeping force for the         purposes of Part IV of that Act; immediately before the death of         the person;     -   “armed services widower” means a man who was the partner of:     -   (a) a person who was a veteran for the purposes of any         provisions of the Veterans' Entitlements Act; or     -   (b) a person who was a member of the Forces for the purposes of         Part IV of that Act; or     -   (c) a person who was a member of a peacekeeping force for the         purposes of Part IV of that Act; immediately before the death of         the person;     -   “illness separated couple” has the meaning given by subsection         (7);     -   “member of a couple” has the meaning given by subsections (2),         (3), (3A) [reference to new section added] and (6);     -   “partner”, in relation to a person who is a member of a couple,         means the other member of the couple;     -   “partnered” has the meaning given by subsection (11);     -   “partnered (partner getting benefit)” has the meaning given by         subsection (11);     -   “partnered (partner getting neither pension nor benefit)” has         the meaning given by subsection (11);     -   “partnered (partner getting pension)” has the meaning given by         subsection (11);     -   “partnered (partner getting pension or benefit)” has the meaning         given by subsection (11);     -   “partnered (partner in gaol)” has the meaning given by         subsection (11);     -   “respite care couple” has the meaning given by subsection (8).         Member of a Couple—General     -   4 (2) Subject to subsection (3), a person is a member of a         couple for the purposes of this Act if:     -   (a) the person is legally married to another person and is not,         in the Secretary's opinion (formed as mentioned in subsection         (3)), living separately and apart from the other person on a         permanent or indefinite [Words added] basis; or     -   (b) all of the following conditions are met:         -   (i) the person has a relationship [Words is living replaced]             with a person of the opposite sex (in this paragraph called             the “partner”);         -   (ii) the person is not legally married to the partner;         -   (iii) the relationship between the person and the partner             is, in the Secretary's opinion (formed as mentioned in             subsections (3) and (3A)[Words added]), a marriage-like             relationship;         -   (iv) both the person and the partner are over the age of             consent applicable in the State or Territory in which they             live;         -   (v) the person and the partner are not within a prohibited             relationship for the purposes of section 23B of the Marriage             Act 1961.             Note: a prohibited relationship for the purposes of section             23B of the Marriage Act 1961 is a relationship between a             person and:     -   an ancestor of the person; or     -   a descendant of the person; or     -   a brother or sister of the person (whether of the whole blood or         the part-blood).         Member of a Couple—Criteria for Forming Opinion About         Relationship     -   4 (3) In forming an opinion about the relationship between 2         people for the purposes of paragraph (2) (a) or         subparagraph (2) (b) (iii), the Secretary is to have regard to         all the circumstances of the relationship including, in         particular, the following matters:     -   (a) the financial aspects of the relationship, including:         -   (i) any joint ownership of real estate or other major assets             and any joint liabilities: and         -   (ii) any significant pooling of financial resources             especially in relation to major financial commitments; and         -   (iii) any legal obligations owed by one person in respect of             the other person; and         -   (iv) the basis of any sharing of day-to-day household             expenses;     -   (b) the nature of the household, including:         -   (i) any joint responsibility for providing care or support             of children: and         -   (ii) the living arrangements of the people; and         -   (iii) the basis on which responsibility for housework is             distributed;     -   (c) the social aspects of the relationship, including:         -   (i) whether the people hold themselves out as married to             each other; and         -   (ii) the assessment of friends and regular associates of the             people about the nature of their relationship; and         -   (iii) the basis on which the people make plans for, or             engage in, joint social activities;     -   (d) any sexual relationship between the people;     -   (e) the nature of the people's commitment to each other,         including:         -   (i) the length of the relationship; and         -   (ii) the nature of any companionship and emotional support             that the people provide to each other; and         -   (iii) whether the people consider that the relationship is             likely to continue indefinitely; and         -   (iv) whether the people see their relationship as a             marriage-like relationship.     -   4 (3A) The Secretary must not form the opinion that the         relationship between a person and his or her partner is a         marriage-like relationship if the person is living separately         and apart from the partner on a permanent or indefinite basis.         [Subsection added]         C 2. Text of Section at Oct. 7, 1995 prior -   SECT 4     Family Relationships Definitions—Couples -   4. SECT 4     Family Relationships Definitions—Couples -   4. (1) In this Act, unless the contrary intention appears:     -   “approved respite care” has the meaning given by subsection (9);     -   “armed services widow” means a woman who was the partner of:     -   (a) a person who was a veteran for the purposes of any         provisions of the Veterans' Entitlements Act; or     -   (b) a person who was a member of the forces for the purposes of         Part IV of that Act; or     -   (c) a person who was a member of a peacekeeping force for the         purposes of Part IV of that Act; immediately before the death of         the person;     -   “armed services widower” means a man who was the partner of:     -   (a) a person who was a veteran for the purposes of any         provisions of the Veterans' Entitlements Act; or     -   (b) a person who was a member of the Forces for the purposes of         Part IV of that Act; or     -   (c) a person who was a member of a Peacekeeping Force for the         purposes of Part IV of that Act; immediately before the death of         the person;     -   “illness separated couple” has the meaning given by subsection         (7);     -   “member of a couple” has the meaning given by subsections (2),         (3), and (6);     -   “partner”, in relation to a person who is a member of a couple,         means the other member of the couple; “partnered” has the         meaning given by subsection (11);     -   “partnered (partner getting benefit)” has the meaning given by         subsection (11);     -   “partnered (partner getting neither pension nor benefit)” has         the meaning given by subsection (11);     -   “partnered (partner getting pension)” has the meaning given by         subsection (11);     -   “partnered (partner getting pension or benefit)” has the meaning         given by subsection (11):     -   “partnered (partner in gaol)” has the meaning given by         subsection (11);     -   “respite care couple” has the meaning given by subsection (8).         Member of a Couple—General     -   4 (2) Subject to subsection (3), a person is a member of a         couple for the purposes of this Act if:     -   (a) the person is legally married to another person and is not,         in the Secretary's opinion (formed as mentioned in subsection         (3)), living separately and apart from the other person on a         permanent basis; or     -   (b) all of the following conditions are met:         -   (i) the person with a person of the opposite sex (in this             paragraph called the “partner”);         -   (ii) the person is not legally married to the partner;         -   (iii) the relationship between the person and the partner             is, in the Secretary's opinion (formed as mentioned in             subsections (3)), a marriage-like relationship;         -   (iv) both the person and the partner are over the age of             consent applicable in the State or Territory in which they             live;         -   (v) the person and the partner are not within a prohibited             relationship for the purposes of section 23B of the Marriage             Act 1961.

Note: a prohibited relationship for the purposes of section 23B of the Marriage Act 1961 is a relationship between a person and:

-   -   an ancestor of the person; or     -   a descendant of the person; or     -   a brother or sister of the person (whether of the whole blood or         the part-blood).         Member of a Couple—Criteria for Forming Opinion About         Relationship     -   4 (3) In forming an opinion about the relationship between 2         people for the purposes of paragraph (2) (a) or         subparagraph (2) (b) (iii), the Secretary is to have regard to         all the circumstances of the relationship including, in         particular, the following matters:     -   (a) the financial aspects of the relationship, including:         -   (i) any joint ownership of real estate or other major assets             and any joint liabilities; and         -   (ii) any significant pooling of financial resources             especially in relation to major financial commitments; and         -   (iii) any legal obligations owed by one person in respect of             the other person; and         -   (iv) the basis of any sharing of day-to-day household             expenses;     -   (b) the nature of the household, including:         -   (i) any joint responsibility for providing care or support             of children; and         -   (ii) the living arrangements of the people; and         -   (iii) the basis on which responsibility for housework is             distributed;     -   (c) the social aspects of the relationship, including:         -   (i) whether the people hold themselves out as married to             each other; and         -   (ii) the assessment of friends and regular associates of the             people about the nature of their relationship; and         -   (iii) the basis on which the people make plans for, or             engage in, joint social activities;     -   (d) any sexual relationship between the people;     -   (e) the nature of the people's commitment to each other,         including:         -   (i) the length of the relationship; and         -   (ii) the nature of any companionship and emotional support             that the people provide to each other; and         -   (iii) whether the people consider that the relationship is             likely to continue indefinitely: and         -   (iv) whether the people see their relationship as a             marriage-like relationship.             D. Amending Act 1995 No 105 amending Section 14

-   Social Security (Non-Budget Measures) Legislation Amendment Act 1995     No. 105

-   of 1995-SECT 14     Family Relationships Definitions—Couples

-   SECT     -   14. Section 4 of the Principal Act is amended:     -   (a) by inserting in the definition of “member of a couple” in         subsection (1), “(3A)” after “(3)”;     -   (b) by inserting in paragraph (2)(a) “or indefinite” after         “permanent”;     -   (c) by omitting from subparagraph (2)(b)(i) “is living” and         substituting “has a relationship”;     -   (d) by omitting from subparagraph (2)(b)(iii) “subsection (3)”         and substituting “subsections (3) and (3A)”;     -   (e) by inserting after subsection (3):     -   “(3A) The Secretary must not form the opinion that the         relationship between a person and his or her partner is a         marriage-like relationship if the person is living separately         and apart from the partner on a permanent or indefinite basis.”.

Appendix C

Relational Database Specifications

Table of Contents

Database Tables Entry Procedure

-   [A] General -   [A 01] Introduction -   [A 02] General Purpose and Structure of the Database\ -   [A 03] General Note about Dates Required for Fields in Database     Tables -   [B] Master Table -   [B 01]ID Field -   [B 02]Date of Assent/Date of Notification Field -   [B 03]Short Title Field -   [B 04]Date of Commencement Field -   [B 04.1] Other forms of commencement or notification -   [B 05]Date of Expiry Field -   [B 06]Type Field -   [B 07]Reprint No Field -   [B 08]Reprint Date Field -   [C] Textblock Table -   [C 01]When the should it be used? -   [C 02]ID Field -   [C 03]Textblock ID1 -   [C 04]Textblock ID2 -   [C 05]Date of Commencement Field -   [C 06]Date of Expiry Field -   Commonwealth Project -   Chapter XX—Database Tables Entry Procedure -   [A] General     [A 01] Introduction     -   This Chapter is divided into three topics; -   [A] This General topic, -   [B] The Master Table of the Data Base; and -   [C] The Textblock Table of the Data Base.     -   All text like this in 10 pt Arial font size is “explanatory text         and notes” on the data base.     -   All text in Courier 9 pt font size with a rule on the left hand         side is the text used for examples, the text is taken from the         Commonwealth data where possible to make it look like the real         thing, however, some examples have been created for the purposes         of explanation and do not exist in the data itself.     -   References in capitals to ACT(S) or REGULATION(S) are references         to the whole Acts or Regulations. The word regulation when         written with a lower case “r” will refer to a numbered         regulation (eg: regulation 2). Note: this does not apply to the         text of examples which have been left as they appear in the         data.     -   The word Section written with a capital “S” will refer to the         numbered section of an ACT (eg: Section 2). Note: this does not         apply to the text of examples which have been left as they         appear in the data.     -   The word Part written with a capital “P” will refer to the means         of dividing an ACT known as a Part (eg: Part 2 or Part II).         Note: this does not apply to the text of examples which have         been left as they appear in the data.     -   Note: the reference to Sections in Commonwealth ACTS and         regulations in Commonwealth REGULATIONS is by way of the lowest         piece of text first, eg: 8(8)(a) would be written “paragraph         8(8)(a)” not “Section 8(8)(a)”.

Note: Fields are out of database structure order in the examples because they appear at different places in the legislation to the structure used in the database tables.

[A 02] General Purpose and Structure of the Database

Purpose

-   To provide a means of managing, monitoring and checking the content     of the Commonwealth Legislation Consolidation. -   To allow the time based (versioning) capacity of the DTD and SGML     coding being under taken to be realised.

Basic Structure

-   The database is to consist of two tables. -   These Tables will be known as MASTER and TEXTBLOCK. -   The specific purpose of each Table will be as follows: -   MASTER will focus on fields that collect data about an ACT or     REGULATION as a whole. -   TEXTBLOCK will focus on specific sub-elements of the whole of an ACT     or REGULATION.     [A 03] General Note about Dates Required for Fields in Database     Tables

Dates in the Database will be used primarily to identify two things:

-   -   the beginning of a whole or part of an ACT or REGULATION, or     -   the end of the whole or part of an ACT or REGULATION

Entries for dates will all be in the dd/mm/yy formula.

There are 3 ways dates will be appear in the legislation:

-   -   specific—are stated in the legislation itself (for example, Date         of Assent)     -   to be advised—are to be published or advised elsewhere (for         example, proclaimed in Gazette)     -   conditional—are based on something else happening (for example,         the commencement of another ACT or REGULATION, the creation of         or termination of an organisation, the happening of an event)         [B] Master Table         [B 01] ID Field

This is the most important field in the database as it ties all the remaining fields and their information together.

For the example used here, that is, the Social Security Act this will be Act-19910046. This is arrived at by combining,

-   (i) the type of legislation, in this case an ACT—see (a) below, then -   (ii) the year of enactment/creation, in this case 1991—see (b)     below, and finally, -   (iii) the ACT'S Number—see (c) below.

All three parts of the ID are important. Inputting the right type, that is, Act for ACTS and Reg for REGULATION etc., and the right year and number is critical as only the correct combination of all three will give the required accuracy.

In the ID field the year and number are separated by a hyphen. Also four digits must be used for the year number, thus 0046 and not 46 is used for the ACT'S number in this example.

An important point to note is that it is possible for an ACT or REGULATION to be known as say the Federal Law Act 1996 but to be Act No 2 of 1997, so that its ID then will be Act-19970002

-   $$# -   $$T -   Social Security (a) Act 1991     -   Updated as at 10 Jul. 1995 -   $$T -   *1* The Social Security Act 1991 as shown in this reprint comprises     Act No. (c) 46, (b) 1991 amended as indicated in the Tables below.<     [B 02] Date of Assent/Date of Notification Field

This will appear in different places according to the style and type of information.

For ACTS use the Table of Acts at the column Date of Assent. The entry for Act No 46, 1991 being the entry for the principal ACT, that is the Social Security Act, is the place to look and the second column shows the date of assent as 23 Apr. 1991 (see (d) below).

Table of Acts< Application< saving or< Act Number Date of Date of transitional< and year assent commencement provisions< Social Security Act 1991< 46, 1991 (d)23 Apr. 1991 1 Jul. 1991<

For REGULATIONS use the Table of Statutory Rules at the column Date of Notification. The entry for REGULATION No 36, 1990 being the entry for the principal REGULATIONS, that is the Cash Transactions Reports Regulations, is the place to look and the second column shows the date of notification as 27 Feb. 1990 (see (e) below).

*1* The Cash Transaction Reports Regulations (in force under the Cash Transaction Reports Act 1988) as shown in this reprint comprise Statutory Rules 1990 No. 36 amended as indicated in the Tables below.

Table of Statutory Rules Date of Application, saving notification Date of or transitional Year and Number in Gazette commencement provisions 1990 No. 36 (e)27 Feb. 1990 27 Feb. 1990 [B 03] Short Title Field

This usually appears in Section 1 of an ACT or regulation 1 of a REGULATION. This is the best place to take the name from as it is the legislated/official way that the ACT, REGULATION etc., is to be referred to etc. See (f) below.

The name should be entered in full (no abbreviations).

You should include the year even though it is part of the ID and also the words ACT or REGULATION. This will firstly, provide a cross check as normally these should match. It will also indicate those ACTS or REGULATIONS where the Short Title Year is different to the Year and Number in the ID field.

-   $$A -   $$T -   Social Security Act 1991—Sect 1< -   Short title -   $$T -   $$NSECT -   1. This Act may be cited as the (f) Social Security Act 1991. *1*     $$S     [B 04] Date of Commencement Field

This information usually appears in Section 2 for an ACT and regulation 2 for a REGULATION.

This is the best place to take the date of commencement from as here it is part of the legislation/the law and therefore always correct (even if its wrong). If taken from the Table of Acts or Table of Regulations an error would not be correct even if not made by us because technically; Tables, Title Pages and even side/margin notes are not considered part of legislation.

-   See (g) below for an example. -   $$T -   Social Security Act 1991—Sect 2< -   Commencement -   $$T -   $NSECT -   2. This Act commences on (g) 1 Jul. 1991. -   $$A -   $$T     [B 04.1] Other forms of commencement or notification

The example given at (g) above is a simple form of commencement in that one date is stated in Section 2.

There are other forms of commencement as follows:

-   24. ACTS or REGULATIONS where no date of commencement is specified     enacted on or before 31, Dec. 1937 (that is, there is no Section 2     and no other section dealing with commencement) commence on the day     on which the ACT was assented to for ACTS (for example, the Acts     Interpretation Act 1901 assented to on Dec. 7, 1901). These Acts     require no entry in the MASTER TABLE as the Date of Commencement and     Date of Assent are the same. -   25. ACTS or REGULATIONS where no date of commencement is specified     enacted on or after Jan. 1, 1938 (that is, there is no Section 2 and     no other section dealing with commencement) then the Act by default     commences on 28th day after the Date of Assent. These Acts do     require an entry in the MASTER TABLE as the Date of Commencement and     Date of Assent are not the same. -   26. ACTS or REGULATIONS where various Parts, Sections, regulations     etc., commence on different dates or on dates to be proclaimed or     notified in Gazette. -   27. ACTS or REGULATIONS where various Parts, Sections, regulations     etc., commence the commencement of another ACT, REGULATION or Part     or Section of another ACT or REGULATION etc.

Note: With respect to the calculation of time (as for example, in the case of commencement 28 days after assent) Section 36 of the Acts Interpretation Act affects how this is done. Section 36 provides:

-   28. Where in an ACT any period of time, dating from a given day,     act, or event, is prescribed or allowed for any purpose, the time     shall, unless the contrary intention appears, be reckoned exclusive     of such day or of the day of such act or event. -   29. Where the last day of any period prescribed or allowed by an ACT     for the doing of anything falls on a Saturday, on a Sunday or on a     day which is a public holiday or a bank holiday in the place in     which the thing is to be or may be done, the thing may be done on     the first day following which is not a Saturday, a Sunday or a     public holiday or bank holiday in that place.

The above will be handled in Australia with respect ot those ACTS or REGULATIONS to which this applies.

[B 05] Date of Expiry Field

This is the opposite of commencement; that is, it indicates when the whole of an ACT or REGULATION or some Part, Section or regulation in an ACT or REGULATION ceases to have effect.

Note: because the expiry is provided for in the ACT or REGULATION itself, this is different to a repeal. The effect is however, the same.

Sections or Regulations relevant to this field are headed “Sunset clause” or “Sunset provision” see (h) below.

Note: the use of the words “unless sooner repealed” in the examples below. This means entries will need to be checked or reviewed to ensure that ACT or REGULATION has not been sooner repealed.

The date or timing of expiry is indicated/expressed in a few different ways: by a specific date, see (i) below.

by a period of years, see (j) below.

30. Examples of expiry of the whole ACT by a specific date.

-   Australian Meat And Live-Stock (Quotas) Act 1990—Updated as at 18     Jul. 1995 -   . . . -   Sect 9 -   Sunset clause (h) -   9. This Act, unless sooner repealed, shall cease to be in force at     the (i) end of 30 Jun. 1998.

Note: the example above uses the words “cease to be in force” and the one below the words “ceases to have effect”. The result is still the same for our purpose.

-   Meat And Live-Stock Industry Act 1995 No. 67 of 1995 -   Assented to 30 Jun. 1995 -   Sect 227 -   Sunset clause -   227. This Act, unless sooner repealed, ceases to have effect at the     end of 30 Jun. 1998.     31. Example of expiry of Part, Division, Subdivision or Section of     ACT after a specified period of years. -   Native Title Act 1993 -   Updated as at 30 Jun. 1995 -   . . . -   Sect 207 -   Sunset provision -   207. This Part ceases to be in force at the (j) end of 5 years after     the Parliamentary Joint Committee is first appointed.     32. Examples of expiry of a portion of a REGULATION -   Federal Court Rules -   Updated as at 22 Mar. 1996 -   . . . -   Order 75 Native Title Rules -   Native Title Act 1993 -   . . . -   Order 75 -   Rule 21 -   Sunset provision -   21. Order 75 ceases to be in force on 1 Mar. 1997. -   Migration (1993) Regulations—Updated as at 25 Jul. 1994 -   . . . -   Reg 2A -   10A -   Sunset provision -   2A.10A. No application may be made under this Division on or after 1     Jul. 1993.     [B 06] Type Field

This Field provides more specific information about the type of legislation. It is different to the ID Field described above which gives the legislation a unique ID. This Field uses three single character codes to describe the legislation.

These are as follows:

-   P=Principal ACTS or REGULATIONS. -   It indicates that this is the main or Principal ACT or REGULATION. -   OR In other words the ACT or REGULATION which gets amended. -   Principal ACTS or REGULATIONS can be either in existence (enacted in     previous years) or newly enacted (created in the current year).

There is nothing specifically unique or different in a principal ACT or REGULATION that makes it easy to identify. By elimination it is however, possible to say what is not a Principal ACT or REGULATION. This is done by looking at the ACT or REGULATION'S title information. Amending Acts or Regulations (which are dealt with next) usually contain the word's “Amending”, “Amendment”, “Repeal” or “Statute Law Revision” in their Short Title. Another indicator in the case of ACTS is that the Long Title will also contain the word's “Amending”, “Amendment”, “Repeal” or “Statute Law Revision” (REGULATIONS however, do not have a Long Title).

The example marked (K) and (J) below shows the Long and Short Titles for a Principal Act known as the Trade Practices Act. (Compare these examples with the ones marked (L) and 20 (M) below).

-   LONG TITLE (K) -   An Act relating to certain Trade Practices -   PART I—PRELIMINARY -   SECT 1 -   Short title (J) -   1. This Act may be cited as the Trade Practices Act 1974.*1* -   SEE NOTES TO FIRST ARTICLE OF THIS CHAPTER.

Note: A principal ACT or REGULATION can contain amendments to other ACTS or REGULATIONS. It therefore, still needs to be considered for its effect on other ACTS.

-   A=Amending ACTS or REGULATIONS. -   It indicates that this is a changing or Amending ACT or REGULATION. -   OR In other words the ACT or REGULATION which does the amending.

Amending ACTS or REGULATIONS will not generally exist in their own right in the consolidated information for which we are creating the data base. The changes they effect will nearly always become part of the Principal ACT or REGULATION.

There are some rare exceptions to the above point however, which will need to be identified (the way to do this most effectively will be to identify them in Australia and provide a list or table of what these ACTS and REGULATIONS are).

As already stated the best ways to identify an Amending ACT or REGULATION are:

Amending ACTS or REGULATIONS will nearly always contain the word's “Amending”, “Amendment”, “Repeal” or “Statute Law Revision” in their Short Title.

For Acts (but not Regulations) there is also a Long Title at the very beginning of the Act (usually before Section 1) which will also contain the word's “Amending” “Amendment”, “Repeal” or “Statute Law Revision”.

The example marked (L) and (M) below shows the Long and Short Titles for the Amending ACT known as the Trade Practices (Secondary Boycotts) Amendment Act 1979.

-   LONG TITLE (L) -   An Act to amend the Trade Practices Act 1974 with respect Secondary     Boycotts and other industrial practices. -   Part I—Preliminary -   Sect 1 -   Short title (M) -   1. This Act may be cited as the Trade Practices (Secondary Boycotts)     Amendment Act 1979.*1* -   SEE NOTES TO FIRST ARTICLE OF THIS CHAPTER.

Note: An Amending ACT or REGULATION can be amended itself by a further amending ACT or REGULATION.

More Examples of Amending ACTS and REGULATIONS

Following are some more examples of Amending ACTS and REGULATIONS and what to look for.

Statute Law Revision Acts

Below are two examples of these. Usually, this is clean up legislation which makes many changes and often effects a larger number of ACTS. They can be specific as in the case of the Decimal Currency example or they can be general as in the case of the 1973 example.

They can both change (amend Parts, Divisions and Sections of ACTS and REGULATIONS) and/or delete (repeal) whole ACTS and REGULATION or Parts, Divisions and Sections.

-   Statute Law Revision (Decimal Currency) Act 1966 -   Statute Law Revision Act 1973

There are other form of Amending ACT similar to the Statute Law Revision Acts as follows:

-   A.C.T. Self-Government (Consequential Provisions) Regulations 1989     No. 3 -   Defence Legislation Amendment Act 1984 -   Fringe Benefits Tax (Miscellaneous Provisions) Act 1986 -   Statute Law (Miscellaneous Provisions) Act (No. 1) 1986 -   Taxation Laws Amendment Act (No. 3) 1986

The above can usually be spotted by the use of words such as “Consequential Provisions” “Laws Amendment”, “Legislation Amendment”, “Miscellaneous Provisions” in their Short Titles.

Repeal Acts

Below are two examples of these. One where the term Legislation is used in the title indicating that more many ACTS are being repealed. Again this is often clean up legislation which repeals many ACTS whose purpose or reason for being has lapsed. Alternatively, as the second example indicates Repeal ACTS can be specific, effecting the repeal of only one ACT.

-   Egg Export Legislation Repeal Act 1984 -   National Welfare Fund Repeal Act     N=Not known

Indicates that the type of the ACT or REGULATION is not known or cannot be determined. These records will the be handled in Australia.

[B 07] Reprint No Field

The information required for this field does not appear in the Commonwealth Data as presently supplied to/held by us. It will need initially to be obtained in the form of a list of existing reprints and their numbers and be added to both the Commonwealth data and the data base as a once only job. It will then need to be maintained on a monthly basis using the two AGPS Pamphlet Publications known as ACTS TABLES for Acts and STATUTORY RULES TABLES for Regulations, the last page in each contains this information for the current year. Note: where the Pamphlets are not available or the reprint number is not known or unavailable then the number 999 should be used to indicate this.

Each of the two tables from the Pamphlets contains the name of the Reprinted ACT or REGULATION in alphabetical order (but see Statutory Rules example below) followed by the date of reprint, then followed by the words “Reprint No.” and a number. It is this last number that needs to be entered.

-   ACTS TABLE entry example -   National Health Act 1935 (20 Sep. 1996) Reprint No. 5     STATUTORY RULES TABLE entry example

Note: Statutory Rules are listed by their parent Act (the Act under which the are made appearing in Italic as shown in the example below).

Banks (Shareholdings) Act 1972

Banks (Shareholdings) Regulations (2 Aug. 1995) Reprint No. 2

[B 08] Reprint Date Field

Like the Reprint Number discussed in [B 07] above the information required for this field does not appear in the Commonwealth Data as presently supplied to/held by us. It too will need initially to be obtained in the form of a list of existing reprints and be added to both the Commonwealth data and the data base as a once only job. It will then need to be maintained on a monthly basis using the two AGPS Pamphlet Publications known as ACTS TABLES for ACTS and STATUTORY RULES TABLES for Regulations, the last page in each contains this information for the current year.

Each of the two tables contains the name of the Reprinted ACT or REGULATION in alphabetical order (but see Statutory Rules example below) followed by the date of reprint, then followed by the words “Reprint No.” and a number.

For this field it is the Date preceding the Reprint Number that needs to be entered. For examples see the examples at [B 07] above.

Note: Again where the Pamphlets are not available or the reprint date is not known or unavailable then the date 00/00/00 should be used to indicate this.

[C] TEXTBLOCK TABLE

[C 01] When the should it be used?

TEXTBLOCK entries will not normally be required for ACTS or REGULATIONS which are either Principal or Reprinted ACTS or REGULATIONS. But note that in the case of Principal ACTS there are exceptions, namely; where the Principal ACT or REGULATION also amends or repeals other ACTS or REGULATIONS.

[C 02]ID FIELD

This field simply repeats the information obtained in [B 01] above. Its purpose is to link this Table with the MASTER TABLE by way of the same ID. For the example, in [B 01] for the Social Security Act the ID was Act-19910046. This ID would be repeated in this field.

[C 03]Textblock ID1

This field is for the ID of the specific Part, Section or regulation in an Amending ACT or REGULATION that causes a change (amendment) to happen.

Textblock ID2 (see [C 04] below) on the other hand records the ID of the specific Part, Section or regulation in an Amending Act or Regulation that is changed (amended).

EXAMPLE 1

Following is an example of an amendment to the Social Security Act which shows how the information required for this field is obtained.

Please note there are several ways in which Amending ACTS and REGULATIONS are presented. However, the information required for this ID field is present in all cases. This first example shows the things to look for and the next example show some of the variations possible.

-   (N) The first thing required is an indication as to type. The     example is an Amending Act. -   (O) The second thing required is the relevant year. In the example     this is 1995. -   (P) The third thing required is the Act or Reg Number. In this     example this is 104. -   (Q) The fourth thing required is the specific Part, Section or     regulation doing the amending. In this example this is SCH1 (ie:     Schedule 1).     The ID entry for this example would then be as follows:     -   ACT-19950104-SCH-1         Social Security Legislation (N) Amendment Act (No. 1) (0) 1995         No. (P) 104 of 1995 -   . . .

(Q)Schedule 1 Section 4< Amendment of the Social Security Act 1991 RELATING TO< the Definition of Income<

-   1. After Paragraph 8 (8) (zf):< -   Insert:< -   “(zfa) a payment of financial supplement made to the person< -   under the Student Financial Supplement Scheme;”.<

EXAMPLE 2

This example shows a different style of amendment to Example 1.

The ID entry for this example would be as follows: ACT-19950105-SEC-4

It would be made up of the following:

-   (R) Indication of Amending Act. (This would be Reg if we were     dealing with a Regulation). -   (S) Year of Act is 1995. -   (T) Act or Reg Number is 105. -   (U) Specific Part, Section or regulation doing the amending is SEC4.     Note: there is no reference to a Schedule (SCH) because Section 4 is     doing the amending.     Social Security (Non-Budget Measures) Legislation (R) Amendment     Act (S) 1995 No. (T) 105 of 1995 -   $$NSECT -   (U)4. Section 198 of the Principal Act is amended by inserting after     subsection (1A): -   $$P -   <     -   “(1B) Subject to subsection (1C), if:<     -   (a) a person; (the ‘carer’) is personally providing constant         care for a severely handicapped person; and<     -   (b) the handicapped person is temporarily absent from Australia         for a period of not more than 3 months; and<     -   (c) the carer accompanies the handicapped person on his or her         absence from Australia;< the carer does not cease to be         qualified for a carer pension merely because of that absence         from Australia. -   $$P -   <     -   “(1C) If during a calendar year, the carer has accompanied the         handicapped person outside Australia on more than one occasion,         the caser ceases to be qualified for carer pension under         subsection (1B) in that calendar year after he or she has,         during that calendar year, qualified for carer pension under         that subsection for periods that together add up to 3 months.”. -   $$A     [C 04] Textblock 102

This field is for the ID of the specific Part, Section or regulation in an Amending ACT or REGULATION that is changed (amended).

Textblock ID1 (see [C 03] above) on the other hand records the ID of the specific Part, Section or regulation in an Amending ACT or REGULATION that causes a change (amendment) to happen.

EXAMPLE 1

Following is an example of an amendment to the Social Security Act which shows how the information required for this field is obtained.

Please note, as with Textblock ID1, there are several ways in which Amending ACTS and REGULATIONS are presented. However, the information required for this ID field is present in all cases. This first example shows the things to look for and the next example shows some of the variations possible.

-   (V) Again the first thing is an indication as to type. The example     is an Amending Act. -   (W) The second thing required is the relevant year. In the example     this is 1991. -   (X) The third thing required is the Act or Reg Number. In this     example this is 46. -   (Y) The fourth thing required is the specific Part, Section or     Regulation that is being amended. In this example this is SEC8.

The ID entry for this example would then be as follows:

-   -   ACT-19910046-SEC-8         Social Security Legislation Amendment Act (No. 1) 1995 No. 104         of 1995

. . .

Schedule 1 Section 4<

Amendment of the Social Security (V) Act (W) 1991

(X) [If not available/reproduced in the Amendment text can be obtained from the main ID field in

Master Table]

Relating To< The Definition Of Income<

-   1. After Paragraph (Y) 8 (8) (zf): -   Insert:< -   “(zfa) a payment of financial supplement made to the person under     the Student Financial Supplement Scheme;”.<

EXAMPLE 2

This example shows a different style of amendment to Example 1.

The ID entry for this example would be as follows: ACT-19950105-SEC-198

It would be made up of the following:

-   (Z) Indication of Amending ACT. (This would be Reg if we were     dealing with a REGULATION). -   (AA) Year of ACT is 1991. -   (BB) The third thing required is the ACT or REGULATION Number. In     this example this is 46. -   (CC) Specific Part, Section or regulation being amended is SEC 198.     Social Security (Non-Budget Measures) Legislation Amendment Act 1995     No. 105 of 1995 -   (Z) (AA) (BB) [if not available/reproduced in the Amendment text can     be obtained from the main ID field in MASTER TABLE] -   $$NSECT -   4. Section (CC)198 of the Principal Act is amended by inserting     after subsection (1A): -   $$P -   <     -   “(1B) Subject to subsection (1C), if:<     -   (a) a person (the ‘carer’) is personally providing constant care         for a severely handicapped person; and <     -   (b) the handicapped person is temporarily absent from Australia         for a period of not more than 3 months; and<     -   (c) the carer accompanies the handicapped person on his or her         absence from Australia;< the carer does not cease to be         qualified for a carer pension merely because of that absence         from Australia. -   $$P -   <     -   “(1C) If, during a calendar year, the carer has accompanied the         handicapped person outside Australia on more than one occasion,         the carer ceases to be qualified for carer pension under         subsection (1B) in that calendar year after he or she has,         during that calendar year, qualified for carer pension under         that subsection for periods that together add up to 3 months.”. -   $$A     [C 05] Date of Commencement Field

This field is for the date an amendment or repeal of a specific Part, Section or regulation commenced. See also [B 04] for information on commencement.

EXAMPLE

Below is an example of a commencement provision from an amending ACT. Note how various sections of the amending ACT are allocated a date of commencement. Using the Section identified in TEXTBLOCK ID1 the date of commencement can be identified and entered in this field.

Thus if the TEXTBLOCK ID1 field were ACT-19950105-SEC-8 then the date information required for this field would be 1 Jul. 1995. See (DD) below.

Social Security (Non-Budget Measures) Legislation Amendment Act 1995 No. 105 of 1995—SECT 2<

Commencement<

-   $$T -   $$NSECT     -   2. (1) Subject to this section, this Act commences on the day on         which it receives the Royal Assent. -   $$P -   <     -   (2) Subdivision A of Division 2 of Part 2 is taken to have         commenced on 1 Jul. 1993. -   $$P -   <     -   (3) Section 8 and 9 are taken to have commenced on (DD) 1 Jul.         1995. -   $$P -   <     -   (4) Section 10 is taken to have commenced on 1 Apr. 1993. -   $$P     [C 06] Date of Expiry Field

This field provides for amendments that are enacted for a period of time, for example; during a special event such as the Olympics.

Note: Expiry provisions are rare and should only be added if clearly specified in the data as in the example below.

EXAMPLE

See (EE) below.

Olympic Security (Non-Budget Measures) Legislation Amendment Act 1997 No. 109 of 1995

-   $$NSECT     -   4. Section 298 of the Principal Act is amended for the period         commencing at midnight on 1 Jul. 1997 and ending on midnight         (EE) 25 Jul. 1997 by inserting after subsection (2A): -   $$P -   <     -   “(2B) Subject to subsection (2C), if:<     -   (a) a person (the ‘carer’) is personality providing constant         care for a severely handicapped person; and<     -   (b) the handicapped person is temporarily absent from Australia         for a period of not more than 3 months; and <     -   (c) the carer accompanies the handicapped person on his or her         absence from Australia;< the carer does not cease to be         qualified for a carer pension merely because of that absence         from Australia. -   $$P -   <     -   “(2C) If, during a calendar year, the carer has accompanied the         handicapped person outside Australia on more than one occasion,         the carer ceases to be qualified for carer pension under         subsection (1B) in that calendar year after he or she has,         during that calendar year, qualified for carer pension under         that subsection for periods that together add up to 3 months. ”. -   $$A

Appendix D Keying Guide for Australian Legislation Documents

General

Validation

All files produced must be parsed against the relevant DTD and each table should be viewed using a suitable Table renderer to make sure that they have been coded correctly.

DTD Modifications

No local modifications must be made to the supplied DTD's. If there are any situations in which it is thought that a change to a DTD is required then the requested change and the reasons for it must be submitted to SGMLSE. If a change is deemed necessary, then the DTD will be changed in the UK and resupplied. This is necessary to maintain consistency in the DTD's being used at both ends in the process.

Files

The SGML files that will be supplied have already been partially processed but will be invalid according to the DTD (especially the tables).

Each file should omit the document type declaration and begin directly with the root element.

Carriage Return Characters

Carriage return characters must not appear in any element which has #PCDATA within its content model. If it is wished to use carriage return characters to shorten line lengths, then they must be placed in position's where they will be ignored by an SGML parser e.g. in places where #PCDATA is not allowed, or within start and end tags in places where separator characters are allowed.

Case

Element and attribute names are case-insensitive. They may be entered in either uppercase, lowercase or a mixture.

Attribute values are usually case-insensitive. The only time that they are case-sensitive is when they have a declared type of CDATA, in which case the string values should be entered directly as they appear in the text.

Markup Minimisation

No non-empty elements have omissible start or end tags, but the empty end tag </> can be used to end the currently open element. A carriage return character can not occur within an empty end tag.

DTD Structure

There are four DTDs and a common element declaration that are used to define the structure of the legislation.

REGS.DTD

This DTD has the public identifier “-//SGMLSE//DTD 1.0 Regulations//EN” and contains the declaration for the regulations. It has two parameter entity references which include“-//SGMLSE//DTD 1.0 Act//EN” and “-//SGMLSE//DTD 1.0 Regulation//EN”. The file regs.sgm produced by the Perl script regs.p/conforms to regs.dtd and calls in all acts as parameter entities.

ACTS.DTD

This DTD has the public identifier “-//SGMLSE//DTD 1.0 Acts//EN” and contains the declaration for the acts. It has a parameter entity references which includes “-//SGMLSE//DTD 1.0 Act//EN”. The file acts.sgm produced by the Perl script acts.pl conforms to acts.dtd and calls in all acts as parameter entities.

ACT.DTD

This DTD has the public identifier “-//SGMLSE//DTD 1.0 Act//EN” and contains the declaration of an act.

REG.DTD

This DTD has the public identifier “-//SGMLSE//DTD 1.0 Regulation//EN” and contains the declaration of a regulation.

COMMON.ELT

This list of elements has the public identifier “-//SGMLSE//ELEMENTS 1.0 Common Elements//EN” and includes element and entity definitions common to all document types.

Character Entities

The character entities allowed have been selected from the ISO public sets isogrk1, isogrk3, isolat1, isonum, isopub and isotech.

These characters are translated one-to-one to the equivalent character in the Times New Roman True Type font.

The <quote> or <blockquote> elements should be used instead to surround any quoted text.

Use Quotes (“) at the beginning and at the end of these elements.

Labels and Identifiers

The major structural elements—act, reg, part, schedule, section, sub, s-sub, ss-sub, . . .

all have a required label attribute (Ibl). Unique identifiers should be generated for these elements. The label for these elements is the preceding number or letter WITHOUT any punctuation or parentheses. For example:

-   1979 No. 141 The charge to income tax—REG 1 -   Income Tax -   1. Fred . . . -   1. (1) This is . . .

<section type=“reg” lbl=“1” ID=“CWACT-19790141-SEC-1”> <title>Income Tax</> <list> <li lbl“1”><p>Fred ...</> <list> <li lbl=“1”><p>This is ...</> </list> </li> </list> </section>

Convert list and Ii items back to the original look in Folio Views, ie to

-   1. Fred . . . -   1. (1) This is . . .     Cross References

All cross references point directly to a target by providing the id of the target as the value of an attribute of the xref element. For details of the format of cross reference identifier strings, see the description of the xref element below.

-   All ID's are marked unchanged as Jump Destinations (JD's). -   <SECTION ID=“CWACT-19950104-SEC-1” LBL=“1”> -   becomes: -   <JD:“=CWACT-19950104-SEC-1”<     REGS DTD ELEMENT     REGS

This is the root element of the Regulations. Its definition is

-   <!ELEMENT regs—(title, header?, reg+)>     That is, it contains a required title element, followed by an     optional header element followed by 1 or more act element.

Not translated

ACTS DTD ELEMENT

ACTS

This is the root element of the Acts. Its definition is

-   <!(ELEMENT acts—(title, header?, act+)>

That is, it contains a required title element, followed by an optional header element followed by 1 or more act element.

Not translated

Reg DTD Elements

Reg

This is the root element of the dtd for a Regulation. Its definition is:

< ! ELEMENT reg - - (title, notes?, provisions?, (preamble | long-title)?, ((order+ | (section | schedule)+ | chapter+ | part+), schedule*)) > < ! ATTLIST reg id ID #REQUIRED lbl CDATA #REQUIRED insert-date NUMBER #IMPLIED insert-leg IDREF #IMPLIED repeal-date NUMBER #IMPLIED repeal-leg IDREF #IMPLIED amend-date NUMBER #IMPLIED amend-leg IDREF #IMPLIED

The insert-date attribute should be used to insert the date YYYYMMDD that the REG was inserted. The insert-leg should be used to insert the ID of the legislation that inserted the REG. The repeal-date attribute should be used to insert the date YYYYMMDD that the REG was repealed. The repeal-leg should be used to insert the ID of the legislation that repealed the REG. The amend-date attribute should be used to insert the date YYYYMMDD that the REG was amended. The amend-leg should be used to insert the ID of the legislation that amended the REG.

The title gets marked up as Level “Heading Level 1”. The period between the insert-date and the repeal-date or amend-date (that is the period during which the above element was in force) gets marked up as follows:

The Folio Views markup used is Groups. See the manual for explanations. We will use three kinds of groups: Inforce-yyyy, Inforce-yyyy-mm and Inforce-yyyy-mm-dd (yyyy can be any year, mm can be any month from 1-12 and dd can be any day from 1-31). If the element was valid throughout a year yyyy, the element becomes a member of the Inforce-yyyy group. If the element was valid only for some months within a year, it becomes a member of the relevant Inforce-yyyy-mm groups. If the element was only valid for some days within a month, the element becomes a member of the relevant Inforce-yyyy-mm-dd groups. Example:

If the element was valid from Jan. 7, 1994 to Jul. 4, 1996, then the element belongs to the following groups: Inforce-94-07, Inforce-94-08, Inforce-94-09, Inforce-94-10, Inforce-94-11, Inforce-94-12, Inforce-95, Inforce-96-01, Inforce-96-02, Inforce-96-03, Inforce-96-04-01, Inforce-96-04-02, Inforce-96-04-03, Inforce-96-04-04, Inforce-96-04-05, Inforce-96-04-06 and Inforce-96-04-07.

Note that the element is not part of the Inforce-94 group because the element wasn't in force throughout of 1994. Nor is the element part of the Inforce-96-04 group because the element wasn't in force throughout April 1996.

If the enduser wants to search for all elements that are valid as of a particular date then the enduser can enter that date in a Query Template in the form DD/MM/YYYY. The Query Template then searches the Folio Views infobase for all elements that belong to the groups Inforce-yyyy, Inforce-yyyy-mm and Inforce-yyyy-mm-dd.

ACT DTD ELEMENTS

ACT

This is the root element of the dtd for an Act. Its definition is

< ! ELEMENT act - - (title, notes?, provisions?, (preamble | long- title)?, (section+ | chapter+ |part+ |sub+)*, schedule*)> <!ATTLIST act id ID #REQUIRED date CDATA #IMPLIED insert-date NUMBER #IMPLIED insert-leg IDREF #IMPLIED repeal-date NUMBER #IMPLIED repeal-leg IDREF #IMPLIED amend-date NUMBER #IMPLIED amend-leg IDREF #IMPLIED <

-   That is, it contains a required title element, followed by optional     notes, provisions, and preamble and either one or more reg, order,     rule, section, chapter or part elements. It has a required id     attribute and implied date attribute -   The insert-date attribute should be used to insert the date YYYYMMDD     that the ACT was inserted. The insert-leg should be used to insert     the ID of the legislation that inserted the ACT. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the ACT was repealed. The repeal-leg should be used to insert     the ID of the legislation that repealed the ACT. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the ACT was amended. The amend-leg should be used to insert the     ID of the legislation that amended the ACT.

EXAMPLES

-   1979 No. 141 The charge to income tax -   <act Ib1=“141” ID=“CWACT-19790141-TXT-0”> -   <title> 1979 No. 141 The charge to income tax</> -   1979 No. 141 The charge to income tax*1* -   <act Ib1=“141” ID=“CWACT-19790141-TXT-0”> -   <title> 1979 No. 141 The charge to income tax<noteref -   ref=“CWACT-19790141-note-1” ></>

The noteref gets marked up as a popup link. The text of the note becomes the text within the popup link.

Treated the same as Reg DTD Elements. See therefor details.

Common Elements

Part

< ! ELEMENT part - - (title, (%plevel;)*, (chapter+ | division+ | section+)*, notes?) < ! ATTLIST part id ID #REQUIRED   lbl CDATA #IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF #IMPLIED >

-   The insert-date attribute should be used to insert the date YYYYMMDD     that the PART was inserted. The insert-leg should be used to insert     the ID of the legislation that inserted the PART. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the PART was repealed. The repeal-leg should be used to insert     the ID of the legislation that repealed the PART. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the PART was amended. The amend-leg should be used to insert     the ID of the legislation that amended the PART.

EXAMPLE

<PART lbl=“1” ID=“CWACT-19790141-PT-1”> <title></title> <p>

The title gets' marked up as Level “Heading Level 2”. Dates get treated the same way as in Regs DTD) Elements. See there for details.

Order

<(ELEMENT order - - (title, (division | section | part | schedule) +) > <!ATTLIST  order id ID #REQUIRED   lbl CDATA #/IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF   #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF   #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF   #IMPLIED >

The insert-date attribute should be used to insert the date YYYYMMDD that the ORDER was inserted. The insert-leg should be used to insert the ID of the legislation that inserted the ORDER.

The repeal-date attribute should be used to insert the date YYYYMMDD that the ORDER was repealed. The repeal-leg should be used to insert the ID of the legislation that repealed the ORDER.

The amend-date attribute should be used to insert the date YYYYMMDD that the ORDER was amended. The amend-leg should be used to insert the ID of the legislation that amended the ORDER.

EXAMPLE

1979 No. 140 FEDERAL COURT RULES - ORDER 3<       ORDER 3<       TIME< $$T $$A $$T 1979 No. 140 FEDERAL COURT RULES - RULE 1< <ORDER lbl=“3” ID=“CWACT-19790140-ORD-3”> <title>TIME</title> <section type=“rule” lbl=“1” ID=“CWACT-19790140-ORD-3.1”> The title gets marked up as Level “Heading Level 2”. Dates get treated the same way as in Regs DTD Elements. See there for details. Division

<(ELEMENT division - - (title, (sub-division+ | section+)) > <(ATTLIST division id ID #/REQUIRED   lbl CDATA #IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF   #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF   #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF   #IMPLIED >

-   The insert-date attribute should be used to insert the date YYYYMMDD     that the DIVISION was inserted. The insert-leg should be used to     insert the ID of the legislation that inserted the DIVISION. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the DIVISION was repealed. The repeal-leg should be used to     insert the ID of the legislation that repealed the DIVISION. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the DIVISION was amended. The amend-leg should be used to     insert the ID of the legislation that amended the DIVISION.

EXAMPLE

1979 No. 140 FEDERAL COURT RULES - DIVISION 1< Division 1-General< $$T $$A $$T 1979 No. 140 FEDERAL COURT RULES - RULE 1< Cases for service of originating process< <DIVISION lbl=“I” ID=“CWACT-I 9790140-DIV-i> <title>General</title> <RULE lbl=“1” ID=“CWACT-I 9790140-DIV-1.1”> <title> Cases for service of originating process </title>

The title gets marked up as Level “Heading Level 3”. Dates get treated the same way as in Regs DTD Elements. See there for details.

<!ELEMENT sub-division - - (title, section+)> <!ATTLIST sub-division id ID #REQUIRED lbl CDATA #IMPLIED insert-date NUMBER #IMPLIED insert-leg IDREF   #IMPLIED repeal date NUMBER #IMPLIED repeal-leg IDREF   #IMPLIED amend-date NUMBER #IMPLIED amend-leg IDREF   #IMPLIED

-   The insert-date attribute should be used to insert the date YYYYMMDD     that the SUB-DIVISION was inserted. The insert-leg should be used to     insert the ID of the legislation that inserted the SUB-DIVISION. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the SUB-DIVISION was repealed. The repeal-leg should be used to     insert the ID of the legislation that repealed the SUB-DIVISION. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the SUB-DIVISION was amended. The amend-leg should be used to     insert the ID of the legislation that amended the SUB-DIVISION. -   The title gets marked up with a Paragraph Style (see Folio Views     Infobase Production Kit Manual for details) ‘Subdivision’, Dates get     treated the same way as in Regs DTD Elements. See there for details.     Provisions -   <!ELEMENT provisions —(title,lblblk)>

EXAMPLE

$$NTABLE     TABLE OF PROVISIONS< $$P Order< $$P   1.  Preliminary< $$P   2.  Sittings and Vacation< <PROVISIONS> <TITLE>TABLE OF PROVISIONS> <TBLBLK> . . </TBLBLK> </PROVISIONS>

Provisions get ignored The Table of Provisions gets generated by the conversion program from the following Elements: Part, Chapter, Order, Division, Subdivision and Section. The generated Table of Provisions is stored just before the first Part, Chapter, Order, Division, Subdivision and Section.

Chapter

<!ELEMENT chapter  - -  (title, %plevel;)*, (part+ | section+ | article+)?)> <!ATTLIST chapter id ID    #REQUIRED lbl CDATA #IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF   #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF   #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF   #IMPLIED >

-   The insert-date attribute should be used to insert the date YYYYMMDD     that the CHAPTER was inserted. The insert-leg should be used to     insert the ID of the legislation that inserted the CHAPTER -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the CHAPTER was repealed. The repeal-leg should be used to     insert the ID of the legislation that repealed the CHAPTER. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the CHAPTER was amended. The amend-leg should be used to insert     the ID of the legislation that amended the CHAPTER. -   The title gets marked up as Level “Heading Level 2”. Dates get     treated the same way as in Regs DTD Elements. See there for details.     Section

This is a sub element of a Regulation. Its definition is:

<!ELEMENT   section   - -   (title, (%unstruct-cont;))> <!ATTLIST section     id   ID #REQUIRED   lbl CDATA  #/IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF   #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF   #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF   #IMPLIED >

-   That is, it contains a required title element, followed by     unstructured content. It has a required Ibl attribute and a required     id attribute. -   The insert-date attribute should be used to insert the date YYYYMMDD     that the SECTION was inserted. The insert-leg should be used to     insert the ID of the legislation that inserted the SECTION. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the SECTION was repealed. The repeal-leg should be used to     insert the ID of the legislation that repealed the SECTION. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the SECTION was amended. The amend-leg should be used to insert     the ID of the legislation that amended the SECTION.

EXAMPLES

-   1979 No. 141 The charge to income tax—SECT. 1 -   Income Tax -   1979 No. 141 The charge to income tax—REG 2 -   Tax -   3. Income tax shall be charged . . .

<section lbl=“1” id=“CWACT-1979141-SEC-1”> <title>Income tax</> <section type = “reg” lbl = “2” id =CWACT1979141-SEC- 1.2” ><title>Tax</title> <p>Income tax shall be charged. . .</>

The title gets marked up as Level “Heading Level 4”. Dates gets treated the same way as in Regs DTD Elements. See there for details.

Schedule

This is a sub element of a Regulation. Its definition is:

<!(ELEMENT schedule - -   (title?,   (%-unstruct-cont;))> <!ATTLIST schedule id  ID  #/REQUIRED   lbl   CDATA  #IMPLIED   insert-date NUMBER #IMPLIED   insert-leg IDREF   #IMPLIED   repeal-date NUMBER #IMPLIED   repeal-leg IDREF   #IMPLIED   amend-date NUMBER #IMPLIED   amend-leg IDREF   #IMPLIED >

-   That is, it contains a required title element, followed by     unstructured content. It has a required Ibl attribute and a required     id attribute. -   The insert-date attribute should be used to insert the date YYYYMMDD     that the SCHEDULE was inserted. The insert-leg should be used to     insert the ID of the legislation that inserted the SCHEDULE. -   The repeal-date attribute should be used to insert the date YYYYMMDD     that the SCHEDULE was repealed. The repeal-leg should be used to     insert the ID of the legislation that repealed the SCHEDULE. -   The amend-date attribute should be used to insert the date YYYYMMDD     that the SCHEDULE was amended. The amend-leg should be used to     insert the ID of the legislation that amended the SCHEDULE.

EXAMPLES

-   1979 No. 141 The charge to income tax—SCHEDULE 1 -   Income Tax -   1. Income tax shall be charged . . .

<schedule lbl = “1” id=“CWACT-1979141-SCH-1”> <title>Income tax</> <p>Income tax shall be charged... </>.

The title gets marked up as Level “Heading Level 2”. Dates get treated the same way as in Regs DTD Elements. See there for details.

Form

<!ELEMENT form - -  (title, formreg, front, back?) > <!ATTLIST form %reqlbl; %reqid;>

Each form has a title, regulation, a front and an optional back. Each has a required Ibl attribute and a required ID.

EXAMPLE

FORM A< Regulation 7< (Front of Form)< COMMONWEALTH OF AUSTRALIA< Trade Practices Act 1974-Sub-section 88 (1)< EXCLUSIONARY PROVISIONS:< APPLICATION FOR AUTHORIZATION<

To the Trade Practices Commission: Application is hereby made under sub-section 88 (1) of the Trade

-   (Back of Form)<     -   DIRECTIONS< -   1. Where there is insufficient space on this form to furnish the     required information, the information is to be shown on separate     sheets, numbered consecutively and signed by or on behalf of the     applicant.

<FORM lbl=“a” ID=“CWACT-I9790141-FORM-A”> <FORMREG>Regulation 7</FORMREG> <FRONT> <AS IS> COMMONWEALTH OF AUSTRALIA<   Trade Practices Act 1974-Sub-section 88 (1)<     EXCLUSIONARY PROVISIONS:<     APPLICATION FOR AUTHORIZATION<

To the Trade Practices Commission: Application is hereby made under sub-section 88 (1) of the Trade

-   Trade -   </ASIS> -   </FRONT> -   <BACK> -   <ASIS> -   Directions<

1. Where there is insufficient space on this form to furnish the required information, the information is to be shown on separate sheets, numbered consecutively and signed by or on behalf of the applicant.

-   </ASIS> -   </BACK> -   </FORM>

Forms get marked up with a Paragraph Style ‘Forms’. The markup of ‘Front’ and ‘Back’ gets inserted as hidden text (hidden text is visible on the screen but doesn't show when the Form gets printed.

FORM ELEMENTS FORMREG <!ELEMENT    formreg - - (#PCDATA) > see above example FRONT <!ELEMENT    front - - (asis) > see above example BACK <!ELEMENT  back   - - (asis) > see above example ASIS <!ELEMENT    asis - -   (#PCDATA) > date is displayed as-is see above example HEADER ELEMENTS HEADER <!ELEMENT   header   - -  (scope?, updated?) > SCOPE <!ELEMENT    scope  - - (% text;)  > UPDATED <!ELEMENT    updated - - (% text;)  > NOTE ELEMENTS NOTES <!ELEMENT    notes -  O  (note+) > List of notes at the start of an act NOTE <!ELEMENT   note   - - (%/plevel;) > <!ATTLIST note id    ID #REQUIRED> A single note

Forms get marked up with a Paragraph Style ‘Forms’. The markup of ‘Front’ and ‘Back’ gets inserted as hidden text (hidden text is visible on the screen but doesn't show when the Form gets printed.

Structural Elements

Title

A generic title, which may occur in several different contexts.

Covered in Acts DTD Elements, Regs DTD Elements and so on.

Inline Elements

Bold

Used to mark any inline text which is set in a bold face other than a title or a label. It may contain text or any inline elements other than <bold>.

It has no attributes.

Ileqn

An inline equation. This is a mathematical equation which is embedded in a line of text characters or other inline elements. See the attached description of equations for further details.

Ital

Used to mark any inline text which is set in a italic face other than a title or a label. It may contain text or any inline elements other than <italic>.

It has no attributes.

Quote

A sequence of text characters or inline elements surrounded by single or double paired quotation marks. The quotation mark characters must not be entered as text characters or entity references as they will be generated automatically.

Subscr

A Subscript (inferior).

Super

A superscript (superior).

Brought over from SGML to Folio Views with no changes.

Cross References

Noteref

A reference to a NOTE element normally used in a TITLE element Implemented as a popup link.

Tempref

A reference to a piece of legislation where the ID is not known. The tempref element will converted to an XREF element at a later date (when the ID is known).

Not converted.

Rngref

A cross reference to a sequential range of targets, e.g. see Sections 3 to 7.

It has two required attributes, startref and endref. Startref is the id of the first of the targets referenced and endref is the id of the last target referenced. For a description of id strings, see the description of the xref element.

Converted as a Query Link.

Xref

A cross reference to a single target. It has a single attribute, ref, which must contain the id string of the target of the reference. Ids are not being entered on elements during keying, but will be generated automatically from the Ibl attribute of elements.

However, for xrefs it is necessary to work out what the id string of the target will be.

The format of id strings is described below:

Converted as a jumplink.

ID Strings

Cross references to sections of Acts and Act Schedules should be marked up using the xref element as described above.

Id strings are made up of four sequential fields separated by a “-” (dash) character as follows

-   field1-field2-field3-field4 -   field 1 is the type of document which is being referenced. The     current valid value is ACT. -   field2 is an abbreviated form of the year and number of the Act,     e.g. 19880001 is 1988 No. 1. -   field3 identifies the type of object being referenced. Valid values     are: -   ORD order -   DIV division -   SCH schedule in an Act -   SEC section in an Act -   CH chapter in anAct -   PT part in an Act -   NOTEa note -   field4 is the identifier of the element being referenced, which is     formed by concatenating the values of the Ibl attributes of the     referenced element and its ancestor elements, separated by a“.”     (point) character. e.g. 1 or 1.1 or 1.1.a or 1.1.a.iv

EXAMPLES

<section lbl=“1”>  <!-- id is ACT-19790141-SEC-1 --> <title>The charge to income tax.</> <list> <li lbl=“1”> <p>Income tax shall be charged. . .</>

Implemented us jumpdestination.

Block Level Elements

Dpeqn

A display equation. This is a mathematical equation which is set on one or more lines by itself.

See the attached description of equations for further details.

It has no attributes.

It has no attributes.

List

A list of related lines of text which are not sub, s-sub or ss-sub elements.

LI

An item in a list. This is a single line of text within a list.

It has a single attribute, marker, which has allowed values of bullet, dash or none, with a default of none. If a marker character precedes the list item then the relevant value should be entered for the attribute. The marker character should not be entered as text. If any marker character other than a bullet or dash is found, contact SGMLSE for a change to the DTD.

P

A single line of text.

Blockquote

A non-inline quote. The quotation mark characters must not be entered as text characters or entity references as they will be generated automatically

TBLBLK

A container element for a table which has a title. It contains a required title element followed by a single table.

It has no attributes.

The above elements get implemented either without conversion or using paragraph styles.

Table Elements

General

Arbortext tables expressed in tagged ASCII form must follow this basic structure:

<table> <rowrule> for each row {     <tablerow>     <cell rule>     for each column     {     <tablecell>text</tablecell>     <cellrule>     }   </tablerow>   <rowrule> } </table> Table

The <table> tag has three required attributes. They must be specified correctly or the table will not be handled properly.

-   ncols=NUMBER The number of columns in the table. This value MUST     agree with the number of columns expressed by the required cwl     attribute. -   Wdm=(25|50═75═100) The numbers indicate the width of the table as a     percentage of the page width. -   cwl=LIST where LIST is a list of integers each separated by a colon.     Each integer represents the relative width of a column.

EXAMPLE

A four column table which is the full width of the page. The second and third columns are twice the width of the first column, and the fourth column is three times the width of the first:

-   <table ncols=“4” wdm=“100” cwl=“1:2:2:3”> -   or, equivalently, -   <table ncols=“4” wdm=“100” cwl=“5:10:10:15”>     Cellrule

Empty element. Specifies a vertical rule. It has a single attribute, rty, which specifies the type of rule. Valid values for rty are:

-   -   “.” (point) for a blank rule,     -   “-” (dash) for a single rule,     -   “=” (equals) for a double rule,     -   “+” (plus) for a bold rule.

EXAMPLE

-   <cellrule rty=“.”> -   for a blank rule, or -   <cellrule rty=“-”> -   for a single rule.     Rowrule

Empty element. Specifies a sequence of horizontal rules, one per cell in the row. It has a single attribute, rtl, which is a colon-delimited list of rule type specifiers. There must be one rule type specifier for each cell in the row. The valid specifiers are as for cellrule above.

EXAMPLE

-   For a four-column table -   <rowrule rtl=“-:.:.:-”> -   would draw a horizontal rule above cells one and four.     Tablerow

Specifies a row in the table. It has a single attribute, hdr, which specifies whether or not the row is a header row in a table which will be repeated over page breaks. The only valid value is “1” (one), which indicates that the row is a header row. An omitted value for hdr indicates that the row is not a header row. A value is only valid on the first <tablerow> in the table.

EXAMPLE

-   <tablerow hdr=“1”>

indicates that the row is a header row (iff the <tablerow> is the first in the table, else it will generate an error).

-   <tablerow>

indicates that the row is not a header row if the <tablerow> is the first in the table.

Tablecell

Indicates a cell in a row in a table. It has four optional attributes:

-   chj=(b|l|r|c) Horizontal justification for that cell. -   b for both right and left justified -   l for flush left, -   r for flush right, -   c for centered.

Default: left justified

-   cvj=(t|c|b) Vertical justification for that cell. -   t for top justified, -   c for centered, or -   b for bottom justified.

Default: top justified

spn=INTEGER For horizontally spanned columns. VAL is a whole number representing how many columns are spanned. Note that for horizontal spans, the text appears in the LEFTMOST cell in the span, and all other cells in the span should be void of text.

-   Default: I

vspn=INTEGER For vertically spanned rows. VAL is a whole number representing how many rows are spanned. Note that for vertical spans, the text appears in the LOWEST cell in the span, and all other cells in the span should be void of text.

-   Default: 1     Arbortext table example

<tbl> <table wdm=“l00” cwl=“3:4:3”> <rowrule rtl=“-:-:-”> <tablerow hdr=“1”> <cellrule rty=“-”> <tablecell>foo</tablecell> <cellrule rty=“-”> <tablecell chj=“c”>fum</tablecell> <cellrule rty=“-”> <tablecell chj=“r” cvj=“b”>fee</tablecell> <cellrule rty“-”> </tablerow> <rowrule rtl“-:-:-”> <tablerow> <cellrule rty=“-”> <tablecell spn=“2” chj=“c”>spanned</tablecell> <cellrule rty=“-”> <tablecell chj=“c”>ugh</tablecell> <cellrule rty=“-”> </tablerow> <rowrule rtl=“-:-:-”> </table> </tbl>

Tables get converted to Microsoft Word tables and then converted into Folio Views.

Equation Elements

General

This maths DTD is a subset of the Arbortext maths DTD, which itself is derived from the AAP maths DTD.

In maths mode, all spaces are ignored (except in a <phr> element as described below). Correct spacing is handled automatically.

-   All alphabetical characters and symbols are treated as variables and     set in italic face, unless they occur within <phr>, <rm> or <rf>     elements. -   All numeric characters and operators are set in roman face, unless     they occur within an <it>element. -   Greek symbols should be entered using the <g> element rather than     entity references. E.g. <g>a</g> produces alpha, <g>b</g> beta, etc.     Any entity references for Greek characters which appear in equations     will be flagged as errors by the parsing program. -   B -   Bold text in an equation. -   DE -   Denominator of a fraction. -   F -   Inline equation. -   FD -   Display equation. -   FEN

Fence. A pair of bracketed delimiters. The attribute lp (left post) defines the type of the left delimiter as below, and the following element rp (right post) defines the type of the right delimiter.

<!ATTLIST fen lp (par|sqb|cub|ang|vb) vb -- par left parenthesis ( sqb left square bracket [ cub left curly brace { ang left angle bracket < vb left vertical bar | -->

-   FR -   Fraction. -   G -   Greek character or characters. Valid characters are:

char equivalent entity a alpha b beta c chi d delta D Delta e epsilon 3 epsiv 4 phiv f phis F Phi g gamma G Gamma h eta i iota j thetav k kappa l lambda L Lambda m mu n nu p pi 2 piv P Pi q thetas Q Theta r rho s sigma S Sigma 9 rhov t tau u upsilon U Upsilon v sigmav w omega W Omega x xi X Xi y psi Y Psi z zeta

-   INF -   Inferior. Subscript in an equation. -   IT -   Italic text in an equation. -   NU -   Numerator of a fraction. -   OVL -   Overline. -   PHR

Phrase. In a phrase all characters are set in roman face and keyed space characters are preserved. A phrase is essentially a temporary escape out of maths mode back into normal text mode.

-   RAD

Radical or root. Contains a radicand (<rcd>), which is the constructs which appear beneath the top horizontal bar, and an optional radix (rdx), which is the power of the root (e.g. square, cube, 4, etc.).

-   RCD

Radicand. The content of a root construct.

-   RDX

Radix. The power of a root.

-   RF

Roman Function. A function name set in roman face, such as log, sin, cos, lim, arg, etc. It differs from the <rm> element in that preceding and following space characters are generated to separate it from surrounding characters.

-   RM

Roman face. Used to force an alpha character to be displayed in normal face rather than be treated as a variable and displayed in italic face.

-   RP

Right delimiter of a fence. It has a single attribute, post, which defines the type of the delimiter. Valid values are the same as for the lp attribute of the <fen> element, except that they specify the right hand match for the relevant left post.

-   SUP

Superior. A superscript in an equation.

-   UNL -   Underline.     Arbortext equation examples -   . . . by multiplying by the fraction     -   A     -   B         where

<p >. . . by multiplying by the fraction -</> <dpeqn>< fr><nu><rm>A</ ></ ><de><rm>B</ ></ ></></> <p>where -</p>

-   . . . by the formula     -   gross taxable income         -   net assets

<p>. . . by the formula -</> <dpeqn>< fr><nu><phr>gross taxable income </></><de><phr>net assets</ ></></ ></>

Equations get converted to Microsoft Word equations and then converted into Folio Views. Alternatively equations get converted to images and added to Folio Views as images.

Appendix E

APPENDIX E <!SGML  “ISO 8879:1986” --    Arbor Text's default SGML declaration, modified to allow longer id/idref's, and to use a number of special characters within them. -- CHARSET BASESET  “ISO 646-1983//CHARSET International Reference Version (IRV)//ESC 2/5 4/0” DESCSET 0  9   UNUSED 9  2   9 11 2 UNUSED 13 1 13 14 18 UNUSED 32 95 32 127 1 UNUSED 128 128 “High-order characters” CAPACITY SGMLREF TOTALCAP 200000 ENTCAP   35000 ENTCHCAP 35000 ELEMCAP 35000 GRPCAP   150000 EXGRPCAP 35000 EXNMCAP 35000 ATTCAP   50000 ATTCFICAP 35000 AVGRPCAP 35000 NOTCAP 35000 NOTCHCAP 35000 IDCAP   35000 IDREFCAP 35000 MAPCAP   35000 LKSETCAP 35000 LKNMCAP 35000 SCOPE     DOCUMENT SYNTAX SHUNCHAR 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 127 BASESET “ISO 646-1983//CHARSET International Reference Version (IRV)//ESC 2/5 4/0” DESCSET 0  128  0 128 128  “High-order characters” FUNCTION RE  13 RS 10 SPACE 32 TAB SEPCHAR 9 NAMING  LCNMSTRT “ ” UCNMSTRT “ ” LCNMCHAR “-./[ ]” UCNMCHAR “-./[ ]” NAMECASE GENERAL YES ENTITY NO DELIM GENERAL SGMLREF SHORTREF SGMLREF NAMES     SGMLREF QUANTITY SGMLREF ATTCNT 100 ATTSPLEN 960 BSEQLEN 960 DTAGLEN 16 DTEMPLEN 16 ENTLVL 16 GRPCNT 100 GRPGTCNT 96 GRPLVL 16 LITLEN   800 NAMELEN 64 NORMSEP 2 PILEN 1024 TAGLEN 960 TAGLVL 24 FEATURES MINIMIZE DATATAG NO   OMITTAG  YES RANK NO SHORTTAG YES LINK SIMPLE NO IMPLICIT NO EXPLICIT NO OTHER   CONCUR NO SUBDOC NO FORMAL YES APPINFO NONE> <!DOCTYPE legislation [ <!- DTD for Scantext/Abha Legislation - (C) Turn-Key Systems 1997   History: 1997-10-13: fix hist at beginning of regs 1997-10-07: restore <target> tag 1997-10-02: enhanced support for regulations (hist, unconv etc) --> <!-- useful characters such as &mdash; --> <!ENTITY % ISOpub public “ISO 8879-1986//ENTITIES Publishing//EN”> %ISOpub; <!-- PARAMETER ENTITIES USED TO SIMPLIFY DTD MARKUP --> <!entity % major “schedule|intcon|article|annex|clause|chapter|part|division|subdivn|section|subs ec|reg|subreg” -- major levels --> <!entity % minor “defn|para|subpar1|subpar2|subpar3 |subpar4|point” -- minor levels --> <!entity % secreg “section | reg” -- used where either sections or regs are appropriate --> <!entity % level “%major; | %minor;” -- all levels --> < entity % refs “term | l.ref | h.ref” -- references which can be found in normal text --> <!entity % raw “(rawtext | rawtable | unconverted)*” -- material such as forms which remains as raw text --> <!entity % effect “sc” -- typographical effects (more to be added later) --> <!entity % text “(%refs; | %effect; | #PCDATA)*” -- normal text (including refs defined above) --> <!entity % hnote “hist | note” -- hist and note are temporarily interchangeable --> <!entity % body “(p+ | repealed), (%hnote;)*” -- body of a legislative element --> < !entity % lev.id “((label, desc?) | (desc, label?))” -- reversible level id --> <!-- MASTER ELEMENT --> <!element legislation - - (act | regulations)+ -- Acts and Regs are currently supported --> <!-- DEFINITIONS OF ACTS AND CONSTITUENT ELEMENTS --> <!element act     - - (desc, (%hnote; | %raw;)*, longtitle, preamble?, (chapter+ | part+ | section+), Schedule*, hist*)> <!element longtitle - - (#PCDATA)> <!element preamble - - (p+) +(para)> <!element regulations - - (desc, (%hnote; | %raw;)*, (chapter+ | part+ | reg+), schedule*, hist*)> <!-- MAJOR LEVELS --> <!element chapter - - (label, desc, (%hnote;)*, (((%secreg;)*, part*) | article+))> <!element part - - (label?, desc, hist*, (((%secreg;)*, division*) | (article+ | clause+)))> <!element division - - (label?, desc, (p | %hnote;)*, (((%secreg;)*, subdivn*) | clause+))> <!element subdivn - - (label?, desc, (%hnote;)*, ((%secreg;)+ | clause+))> <!element section - - (%lev.id;, ((subsec +, (modules | module +)?) | repealed))> <!element subsec - - (%lev.id;, ((p, (p | note)*, hist*) | (repealed, note*, hist*)))> <!element modules - - (%lev.id;, module+)> <!element module - - (%lev.id;, (submod + | repealed))> <!element submod - - (%lev.id;, ((p, (p | %hnote; | method | tabloid)*) | (repealed, (%hnote;)*)))> <!element reg - - (label?, desc, hist?, (subreg + | repealed))> <!element subreg - - (label, desc?, hist'?, ((p, (p | note)*, hist*) | (repealed, note*, hist*)))> <!-- SCHEDULES, CONVENTIONS etc --> <!element schedule - - (label?, desc?, hist*, (chapter+ | part+ | section+ item+ | p+ | tabloid+ | intcon)?, %raw;)> <!element intcon - - (desc, preamble, (part+ | division+ | subdivn+ | article+), annex*)> <!element annex - - (label?, desc, p*, (part* | division* | clause* | para*, <!element article - - (label, desc?) para*))> (division* | clause* | para*))> <!element clause - - (((label, desc?) | (desc, label)), p+)> <!element item - - (label?, desc?, %body;)> <!-- DEFINITIONS AND MINOR LEVELS --> <!element defn - - (%body;)> <!element note - - (label?, p+)> <!element hist - - (label?, (p+ | raw;)) <!element point - - (p+)> <!element para - - (label?, %body;)> <!element subpar1 - - (label?, %body;)> <!element subpar2 - - (label?, %body;)> <!element subpar3 - - (label?, %body;)> <!element subpar4 - - (label?, %body;)> <!element method - - (%lev.id;, (p | %hnote; | step)+)> <!element step - - (label, %body;)> <!-- COMMON CONSTITUENT ELEMENTS --> <!element label - - (%text;) -- chapter number, section number, etc. --> <!element desc - - (%text;) -- chapter name, section name, etc. --> <!element term - - (%text;) -- defined term --> <element repealed - o EMPTY -- indicates that the enclosing level has been repealed --> <!element p - - (%minor | refs; | %effect | tabloid | amend | target | #PCDATA)* -- textual paragraph at any level --> <!-- UNCONVERTED MATERIAL --> <!element unconverted - - CDATA -- yet to be converted (eg. complex schedules) --> <!element rawtext - - CDATA -- unconverted text (eg. forms) --> <!element rawtable - - CDATA -- unconverted tables (eg. amended provisions) --> <!-- CROSS-REFERENCES --> <!element l.ref - - (%text;) -- legislation ref --> <!element h.ref - - (%text;) -- history ref --> <!-- AMENDMENT MARKUP--> <!element amend - - (%refs | %effect | quote | #PCDATA)* -- amendment = action + text --> <!element target - - (#PCDATA) -- target of amendment --> <!element quote - - (label | desc | p | %level | %refs | %effect | #PCDATA)* --   quoted material --> <!-- PSEUDO-TABLES --> <!element tabloid - - (label?, desc?, (head | row)+)> <!element head - - (cell+)> <!element row - - (cell+)> <!element cell - - (#PCDATA|p)*> <!-- EFFECTS --> <!element sc -- (#PCDATA) -- small caps --> <!-- ATTRIBUTE LISTS --> <!attlist act  juris (cth | nsw | vic | qld | sa | wa | tas | act | nt |imp)   #REQUIRED -- jurisdiction -- year CDATA #REQUIRED -- year assented -- number  CDATA  #REQUIRED -- act number -- reps CDATA #IMPLIED -- 2nd reading (HR) -- senate CDATA #IMPLIED -- 2nd reading (Sen) -- assent CDATA #IMPLIED -- assent date -- cdate CDATA #IMPLIED -- commencement --> <!attlist regulations juris (cth | nsw | vic | qld | sa | wa | tas | act | nt | imp)   #REQUIRED -- jurisdiction -- Year CDATA #REQUIRED -- year assented -- number  CDATA  #REQUIRED -- act number reps CDATA #IMPLIED -- 2nd reading (HR) -- senate CDATA #IMPLIED -- 2nd reading (Sen) -- notified  CDATA  #IMPLIED -- notification date -- cdate CDATA #IMPLIED -- commencement <!attlist schedule id ID #IMPLIED -- legislation id -- cdate CDATA  #IMPLIED -- commencement -- refsec CDATA #IMPLIED -- referring section --> <!attlist chapter id ID #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement <attlist part id  ID  #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement <!attlist division id ID #IMPLIED -- legislation id -- cdate CDATA  #IMPLIED -- commencement <!attlist subdivn id ID #IMPLIED -- legislation id -- cdate CDATA  #IMPLIED -- commencement <!attlist section id ID #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement --> <attlist subsec id  ID  #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement --> <!attlist reg id  ID  #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement --> <!attlist subreg id ID #IMPLIED -- legislation id -- cdate CDATA #IMPLIED -- commencement --> <!attlist l.ref ref IDREF  #IMPLIED -- legislation idref --> <!attlist term id  ID  #IMPLIED -- term id ]> Industrial Applicability

It is apparent from the above that the arrangements described are applicable to the electronic publishing industry.

The foregoing describes only some embodiments of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive. 

1. A method for electronically publishing text-based data, the method comprising: dividing said text-based data into a plurality of portions of text-based data; amending at least one of said plurality of portions of text-based data; storing said plurality of portions of text-based data; storing said amended portion of text-based data; providing a plurality of attributes, wherein said attributes define at least in part a manner in which at least one of said plurality of portions of text-based data and said amended portion of text-based data is capable of being organized and linked in a multidimensional space; associating at least one of said plurality of portions of text-based data and said amended portion of text-based data with at least one link comprising at least one of code or markup language enabled at least in part by at least one of said plurality of attributes; enabling a user to search said plurality of portions of text-based data and said amended portion of text-based data using at least one of said plurality of attributes; and allowing the results of said search to be published to a user by: allowing the provision of at least one of said plurality of portions of text-based data or said amended portion of text-based data in response to said search; and allowing the provision of one or more selectable links to allow said user to select said one or more selectable links, wherein at least one of said plurality of portions of text-based data related to a current, provided portion based on said current, provided portion's attributes is allowed to be displayed as a graphical representation of at least one dimension of a multidimensional space that is configured to allow a user to select and thereby display text-based data represented by a point on said multidimensional space; wherein said multidimensional space is an unbounded area capable of or involving more than three dimensions.
 2. The method according to claim 1, wherein said searching uses one or more attributes.
 3. The method according to claim 1, wherein said plurality of portions of text-based data and said amended portion of text-based data are encoded using one or more Document Type Definitions (DTD) or Style Sheet Mechanisms (SSM).
 4. The method according to claim 1, wherein said at least one link comprises any data in addition to the text-based data and said amended portion of text-based data.
 5. The method according to claim 1, wherein said at least one link comprises code that allows departure and destination points to be created between said plurality of portions of text-based data and said amended portion of text-based data.
 6. The method according to claim 1, wherein said at least one link comprises an identification code for a corresponding one of said plurality of portions of text-based data and said amended portion of text-based data.
 7. The method according to claim 1, wherein said amended portion of text-based data is amended by performing at least one of the group consisting of adding data to one of said plurality of portions of text-based data, deleting data from one of said plurality of portions of text-based data, and modifying data of one of said plurality of portions of text-based data.
 8. The method according to claim 7 wherein said plurality of portions of text-based data and said amendment portion of text-based data comprises legislation or material related to a provision of said legislation.
 9. The method according to claim 8, wherein each of the plurality of portions of text-based data is a respective provision of said legislation or material related to a provision of said legislation.
 10. The method according to claim 9, wherein said provision is a section, schedule or appendix of an Act or a section, schedule or appendix of a regulation.
 11. The method according to claim 1, wherein at least one of said plurality of predefined portions of text-based data is a block of text-based data that is larger than a single word but smaller than an entire document.
 12. The method according to claim 1, wherein the at least three dimensions are axes along which, or along some combination of which, point-to-point movement is permitted.
 13. The system according to claim 1, wherein a selectable link allows display of a list of versions of at least one of said plurality of predefined portions of text-based data. 